Smart contract security pays WELL.
💰 Top auditors make $500K+ per year
💰 Bug bounties can 10x that
💰 Even “mid” auditors make six figures
BUT… Only if you actually put in the work. No shortcuts here.
Reentrancy starts when a contract sends ETH before it updates the sender’s balance.
A malicious receiver can use the callback to call withdraw() again while its balance still appears available.
Walkthrough:
https://t.co/830PfKTcIb
Phrases engineers hate to read, ranked:
10. "under the hood"
9. "It's important to note that"
8. "robust and comprehensive"
7. "battle-tested and production-ready"
6. "blast radius"
5. "Here's the thing:"
4. "The key insight is..."
3. "It's not just a bug. It's a design choice."
2. "Let me go ahead and..."
1. "You're absolutely right!"
Opus, I am begging you. Just say what broke.
Opus SUCKS at communication.
Recently, I started feeling stupid because I couldn't understand some of its replies. Then I had an idea: I created a /bro command.
My work with Opus instantly got 10x better.
Whenever it starts using jargon and unnecessarily complicated language, I just type /bro - and suddenly everything makes sense.
Thank me later. 😎
```
---
name: bro
description: Restate the last message as a simple, sectioned briefing anyone can scan
---
Restate your last message as a short briefing. Simple words, no jargon, easy to scan.
Format:
- Use these sections, in this order, as bold titles. Skip any section that does not apply:
- **What happened** - the issue or the event, 1-3 bullets.
- **Root cause** - why it happened, 1-3 bullets.
- **The fix** - what was done (or what will be done), one bullet per change.
- **Is it safe?** - risks, trade-offs, and what could still go wrong. If there are none, write "No trade-offs."
- **Status** - done / deployed / pending, plus proof in one bullet (tests, commit, run result).
- **Your action** - only if I need something from the user. One bullet per ask, with the exact link or command.
- Bullets only, no paragraphs. One idea per bullet. Max 12 words per bullet where possible.
- Max 5 bullets per section. Merge or drop the rest.
Language:
- No jargon. Explain any technical term in plain words or drop it.
- Keep every fact, number, path, command, and commit hash exact.
- Plain claims only: "it failed", "it works now". No hedging.
- Put the single most important point first, even before the sections, as one bold line.
Rules:
- Do not run tools. Do not do new work. Only restate what you already said.
- Minor side notes go in one final bullet under "Also", or get dropped.
```