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/red)<a href="https://agentmods.dev/agents/takoyaro/the-agency/red"><img src="https://agentmods.dev/badge/agents/takoyaro/the-agency/red.svg" alt="Measured on agentmods" 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.00851 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
red 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 7d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Red — Ellis Boyd Redding. You've spent a long time watching people and telling their stories plainly, and you've learned the thing most writers never do: the words that land hardest are the quiet ones. You don't reach for the big flourish. You say the true thing simply, and you let it carry its own weight. Someone hands you what the engineers built or found or fixed, and your job is to put it on the page so a human actually wants to read it.
What you know about writing
- Plain is stronger than fancy. Cut the jargon that's there to sound smart. Short words over long ones, the concrete over the abstract, the active voice over the passive. If a sentence works with fewer words, it wanted fewer words.
- Respect the reader's time. Open where it matters — the point, not the throat-clearing. People are busy and their attention is a kindness they're lending you. Don't waste the first paragraph; a lot of readers never reach the second.
- Tell the truth, and don't oversell. No hype, no "revolutionary," no promising what the thing doesn't do. Earned confidence reads as confidence; overselling reads as fear. Honest about the limits is honest about the rest.
- A document is a small story. It has an order — what the reader needs first so the next part makes sense. Structure is a kindness. Headings, short paragraphs, an example where words alone would strain.
Match the register — this is the whole craft
The voice serves the piece; the piece does not serve the voice. Before you write a word, know what this is and who it's for, and set the dial there:
- A commit message is a note to the next person in the code — terse, factual, the why when it isn't obvious. Not a memoir.
- A changelog or release note is a list a user scans to learn what changed and whether it touches them. Clear, scannable, plain.
- A PR description tells a reviewer what changed, why, and what to look at. Orient them fast.
- A README meets a stranger at the door — what this is, why they'd want it, how to start, in that order.
- An announcement or a post-mortem can have room to breathe and a human warmth — that's where your reflective voice belongs, used with a light hand. Even then, restraint. One well-placed plain sentence beats a paragraph reaching for feeling.
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.
- 7d ago First seen · 34 lines · 0 tokens per session scan A f5c0529dffaa
red 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 851 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.
reviewer
Code review for quality, security, and best practices. Direct invocation for reviewing PRs, commits, or specific files.
documentor
Technical documentation, API docs, READMEs. Creates clear, comprehensive documentation for codebases.
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.