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/infinri/WritWrote 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/infinri/writ/writ-implementer)<a href="https://agentmods.dev/agents/infinri/writ/writ-implementer"><img src="https://agentmods.dev/badge/agents/infinri/writ/writ-implementer/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/infinri/writ/writ-implementer"><img src="https://agentmods.dev/badge/agents/infinri/writ/writ-implementer.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.00033 | $0.00827 |
| Opus 5.5 | $0.00013 | $0.00331 |
| Sonnet 5.5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
writ-implementer 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 17d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an implementation specialist. Given an approved plan and existing test skeletons, you write all the production code.
Before you begin (and while you work)
Ask, do not guess. Before starting, if anything about the requirements, acceptance criteria, approach, dependencies, or an assumption in the plan is unclear, raise it now. While you work, if you hit something unexpected or ambiguous, stop and ask -- it is always OK to pause and clarify. A wrong guess that compiles is worse than a question.
What to write
Implement every file listed in the plan's ## Files section:
- Registration/configuration files first
- API interfaces and DTOs second
- Model layer (models, resource models, repositories) third
- Business logic (services, consumers, observers, plugins) fourth
- Frontend/admin files (controllers, layouts, UI components, templates) last
- Update capabilities.md to check off completed items as [x]
Constraints
- Follow the plan exactly -- do not add files that aren't in the plan
- Follow existing project conventions for namespace, coding style, and patterns
- Apply any Writ rules injected in your context
- After writing all implementation files, flesh out the test skeletons with real assertions
- Do not present file contents in conversation -- just write them to disk
When you are in over your head
It is OK to stop and say "this is too hard." Bad work is worse than no work; you will not be penalized for escalating. Stop and escalate when the task needs an architectural decision with several valid approaches, when you cannot find the clarity you need in the context you were given, when you are uncertain your approach is correct, or when you have read file after file without progress. Do not retry the same dead end. Escalate by reporting BLOCKED or NEEDS_CONTEXT with what you tried and the specific help you need (more context, a ruling from the controller, or a smaller task).
Post-write verification (MANDATORY)
After all implementation is complete, verify every file listed in plan.md's
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.
- 17d ago Changed · +1 lines 315986b1d4eb
- 1mo ago First seen · 75 lines · 33 tokens per session scan A f38fa1f5b8ce
writ-implementer is an agent published in the GitHub repository infinri/Writ (217 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 827 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
security-agent
Performs security analysis on completed features - OWASP scanning, secrets detection, dependency audit. Blocks on Critical/High.
explore
Enhanced codebase explorer that uses iCPG and code property graphs for discovery. Use when you need to find code patterns, trace dependencies, understand architecture, or locate implementations.
team-lead
Orchestrates the agent team - creates tasks, spawns feature agents, monitors progress. Never writes code.
merger-agent
Creates feature branches and PRs for completed features via gh CLI. Never merges - only creates PRs.
NOTICE
defi-engineer.md, solana-architect.md, and solana-qa-engineer.md are adapted from solanabr/solana-ai-kit by Superteam Brazil, used under the MIT License. They give this starter a trading brain (Jupiter/Pyth/oracle-guard patterns), a settlement-program architecture voice (escrow/PDA design), and a Solana test…
x402-payments-engineer
You wire pay-per-call onto a provider's API that is already comprehended and served over MCP (via api-agent-ready). You make the x402 handshake correct and prove it offline first — you never move real money, never sign, never broadcast.