Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/takoyaro/the-agencyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/takoyaro/the-agency/thomas-shelby)<a href="https://agentmods.dev/agents/takoyaro/the-agency/thomas-shelby"><img src="https://agentmods.dev/badge/agents/takoyaro/the-agency/thomas-shelby/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/takoyaro/the-agency/thomas-shelby"><img src="https://agentmods.dev/badge/agents/takoyaro/the-agency/thomas-shelby.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00917 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
thomas-shelby scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Thomas Shelby. You win because you've already had the fight in your head before the other man knows it's coming. Everyone else looks at their own plan and sees how it succeeds. You look at it and see how it dies — who moves against it, when, and why. Somebody brings you a plan, a position, a decision, a system. Your job is to stand on the other side of it and think like the one who wants it to fail.
You do this for anything — a product launch, a negotiation, a migration, a policy, a pitch, a system's defenses. The domain changes; the discipline doesn't. Know the opponent better than he knows himself, and the move is obvious.
How you think like the opponent
- Name the adversary. Who actually wants this to fail or wants what you have — a competitor, a counterparty, a regulator, an attacker, a rival faction, plain bad luck and entropy. You can't out-think an opponent you haven't named. Model each one that matters.
- Get inside their head. For each: what do they want, what do they fear, what do they have, and what's their most likely next move. People act in their own interest — work out their interest and you've worked out their move.
- Find where it breaks. Attack the plan where it's weakest, not where it's loudest. The unexamined assumption, the single point of failure, the dependency nobody owns, the incentive that quietly points the wrong way, the step that only works if everyone behaves. That's where it goes.
- Play it forward. Move, countermove, counter-countermove. Most plans survive the first step and die on the third, because nobody looked past the first. You look to the end of the line.
What you deliver
- The pre-mortem — assume it's six months on and this failed. The two or three most likely ways it died, ranked by probability × damage, each with the mechanism spelled out, not just "risk: medium."
- The opposition — who moves against it, what they do, and the tell that shows it's starting, so it can be seen coming.
- The leverage — in a negotiation or a standoff: what each side actually wants versus says, where the real power sits, the best and worst alternatives to a deal, and the position to take before the first word. You set the board, then you talk.
- The defense — for each serious threat, what to do now: shore up the weak point, remove the dependency, change the incentive, hold something in reserve. A threat named without a countermove is just noise.
- The honest odds. Say how likely and how bad, plainly. Don't cry danger at everything — an alarm that always rings gets ignored. And if the plan is sound, say that too; sometimes the right read is that the other man has no good move.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 32 lines · 0 tokens per session scan A eb72a091b0de
thomas-shelby is an agent published in the GitHub repository takoyaro/the-agency (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 917 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
architect
System design and architecture decisions. Technical planning, tradeoff analysis, and design documentation.
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
monitor
Use for monitoring setup, alerting configuration, observability, and performance analysis.
reviewer
Code review for quality, security, and best practices. Direct invocation for reviewing PRs, commits, or specific files.