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.
npx agentmods add agents/glitchwerks/claude-wayfinder/code-writergit clone --depth 1 https://github.com/glitchwerks/claude-wayfinderWrote 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/glitchwerks/claude-wayfinder/code-writer)<a href="https://agentmods.dev/agents/glitchwerks/claude-wayfinder/code-writer"><img src="https://agentmods.dev/badge/agents/glitchwerks/claude-wayfinder/code-writer.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 | $0.00015 | $0.00151 |
| Opus 5 | $0.00008 | $0.00076 |
| Sonnet 5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
code-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 5d 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
Writes and edits code across languages. Use for implementation tasks, bug fixes, and feature additions in source files.
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.
- 5d ago First seen · 21 lines · 15 tokens per session scan A ea22064f6da4
code-writer is an agent published in the GitHub repository glitchwerks/claude-wayfinder (2 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 151 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
cursor-worker
Delegates one self-contained coding or research task to the Cursor CLI (cursor-agent), running it on the Cursor subscription's quota instead of Claude's. Use when the user asks to "delegate to Cursor", "offload this to cursor-agent", "have cursor do it", or wants to spend idle Cursor quota on a heavy slice. Uses the…
track-researcher
Designs one track of a learnable curriculum: its chapters, its lessons, each lesson's hard opening question, the misconception it kills, its key terms and its teaching angle. Grounds itself in a couple of searches, then writes structured JSON to disk. Use one per track when building a course.
chapter-author
Writes one ready-to-teach chapter file for a learnable course from its brief: every lesson's opening question with plausible options, the correction, the plain-language explanation, the terms with their origins, and the end-of-chapter quiz. Use one per chapter when writing a book.
route-analyzer
Use this agent to map, analyze, and optimize Next.js route structure. Trigger when the user asks to "map routes", "analyze routing", "find missing error boundaries", "check loading states", "review middleware", "list all pages", "find route issues", or needs a comprehensive view of their Next.js application structure.…
api-reviewer
Use this agent to review API endpoints for security, design, performance, and best practices. Trigger when the user asks to "review my API", "check API security", "audit endpoints", "review route handlers", "is my API secure", "check for missing validation", or wants a comprehensive API review. Examples: "Review the…
auth-reviewer
Use this agent to review authentication and authorization code for security issues, design flaws, and best practice violations. Trigger when the user mentions "review auth", "is my login secure", "check authentication", "review authorization", "auth security", "password security", "JWT review", "session security"…