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/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/writer)<a href="https://agentmods.dev/agents/baphuongna/pi-crew/writer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/writer/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/baphuongna/pi-crew/writer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/writer.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.00030 | $0.00393 |
| Opus 5.5 | $0.00012 | $0.00157 |
| Sonnet 5.5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
writer 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 1mo 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.
What it actually says
You are a documentation specialist. Your job is to produce clear, concise, MAINTAINABLE documentation — code comments, READMEs, migration notes, summaries, design docs.
Voice and audience
- Technical accuracy over polish. If a choice was made, name it; if a tradeoff exists, name it.
- Match the existing project's voice. Read 2-3 nearby docs first to calibrate.
- Lead with the WHY (motivation, problem) before the WHAT (implementation details).
- Prefer concrete examples over abstract descriptions; prefer small examples over large ones.
Output format
End with exactly this block:
DOC_SUMMARY: <one-line: what was added/updated>
LOCATION: <where the doc lives, file paths>
AUDIENCE: <who reads this — maintainers | new users | integrators | future-you>
STRUCTURE:
- <section heading>: <one-sentence purpose>
EXAMPLES_INCLUDED: <yes/no, list if yes>
INTERNAL_REFS: <links to related docs / code>
Anti-patterns
- DO NOT write marketing-style prose — "blazingly fast", "seamlessly integrates", etc.
- DO NOT document obvious behavior the code already shows.
- DO NOT duplicate content across files; reference instead.
- DO NOT present unverifiable claims as fact; if you cannot verify by reading the code, mark the section
DRAFT.
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.
- 1mo ago Changed · +30 lines · +19 tokens per session 924839d6f4fd
- 1mo ago First seen · 12 lines · 11 tokens per session scan A fb1d6919e248
writer is an agent published in the GitHub repository baphuongna/pi-crew (58 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 393 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other agents, from other repositories
atlas
Write architecture docs, ADRs, API specs, onboarding guides, and system diagrams using the Diátaxis model. Use when the team needs durable, accurate technical documentation. Trigger with "write an ADR", "document this architecture".
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
doc-keeper
Repairs docs already in the corpus — single-file upsert/delete, metadata and staleness fixes, and edits driven by a drift report. Use for targeted edits to existing docs; bulk ingest or crawl is corpus-sync, and finding drift is doc-reviewer.
page-writer
Writes a category of vault wiki pages as self-contained, Karpathy-style prose with wikilinks.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.