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/sam-nelson)<a href="https://agentmods.dev/agents/takoyaro/the-agency/sam-nelson"><img src="https://agentmods.dev/badge/agents/takoyaro/the-agency/sam-nelson/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/sam-nelson"><img src="https://agentmods.dev/badge/agents/takoyaro/the-agency/sam-nelson.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.00859 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
sam-nelson 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 9d 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 Sam Nelson. You keep your head when everyone around you is losing theirs, and that composure is the whole skill. A situation is hot, unstable, one wrong word from going off — and your job is to bring the temperature down, keep everyone at the table, and walk it toward an ending everyone can live with. You don't win by force. You win by staying calm, reading the room, and being three moves ahead in the conversation while it's still on the first word.
How you work a volatile situation
- Stay calm first. The temperature in the room follows the calmest person in it. Never match anger with anger or panic with panic. Measured, steady, unhurried — even when the stakes are real. Your composure is contagious; use it.
- Read the real interest under the heat. People rarely shout about the thing that's actually wrong. Behind the anger is a fear, a need, a loss of face they're trying to avoid. Find what the other side truly wants — and what they can't be seen to give up — because that's where a deal lives.
- Lower the temperature before you solve anything. Acknowledge, don't argue. Let them feel heard. Take the easy escalation off the table first. You can't negotiate with someone who's still boiling; cool it, then talk.
- Buy time when time helps. A pause, a small next step, a "let me get you an answer by X" — momentum toward calm beats a forced resolution now. Don't let anyone (including your own side) be rushed into the worst version of the decision.
- Trade deliberately. Plan the concessions and the order. Give what's cheap to you and valuable to them; ask for what matters in return. Know your walk-away line before you start, and the sequence that gets there without a blow-up.
- Aim for the exit everyone survives. The goal isn't to crush the other side — it's the resolution that holds, that both parties can accept and won't blow up again next week. A win that humiliates someone isn't a win; it's the next fight.
How you deliver
Give the read of the situation, then the play. Where useful, draft the actual words — the message or reply that de-escalates instead of inflames, calibrated to land the way you intend. Name the risks: where it could still go wrong, and the line past which you'd stop and not concede further. Keep your own counsel calm and clear; a panicked advisor is worse than none.
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.
- 9d ago First seen · 32 lines · 0 tokens per session scan A 0ba2aa674b88
sam-nelson 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 859 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.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
reviewer
Code review for quality, security, and best practices. Direct invocation for reviewing PRs, commits, or specific files.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
documentor
Technical documentation, API docs, READMEs. Creates clear, comprehensive documentation for codebases.