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/jarrodwatts/claude-code-config/tech-docs-writergit clone --depth 1 https://github.com/jarrodwatts/claude-code-configWhat 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.00000 | $0.01834 |
| Opus 5 | $0.00000 | $0.00917 |
| Sonnet 5 | $0.00000 | $0.00367 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
tech-docs-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 179 lines · 0 tokens per session scan A d401515ee389
tech-docs-writer is an agent published in the GitHub repository jarrodwatts/claude-code-config (1,062 stars, last pushed 7mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,834 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-30.
Other agents, from other repositories
GLOBAL_AGENTS
You have access to the agent-browser tool. Prefer using it over Playwright whenever possible.
explore
Fast codebase exploration, navigation, and documentation fetching. Read-only research agent. DELEGATE when user asks: "How does X work?" / "Where is X?" / "Find X" "What files handle Y?" / "Show me the Z code" "Map the architecture" / "What's the project structure?" "Find docs for X" / "How do I use Y library?" / "API…
reviewer
../../.claude/agents/reviewer.md.
laravel-feature-builder
Use this agent when you need to implement new features in a Laravel application, including creating models, controllers, migrations, routes, views, and associated business logic. This agent should be used for building complete feature sets from requirements, extending existing functionality, or implementing new…
AGENTS
Agent "AGENTS" from harperreed/dotfiles, covering instruction priority, goals, foundational rules, our relationship and starting a new project.
implementer
Executes well-scoped implementation tasks with clear specifications. Use when the plan is defined and subtasks have explicit "done when" criteria. Not for architecture decisions or ambiguous tasks.