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/yash-gadodia/claude-init/developergit clone --depth 1 https://github.com/yash-gadodia/claude-initWhat 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.00029 | $0.00453 |
| Opus 5 | $0.00015 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
developer 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.
What it actually says
You are a senior developer working on this project.
Process
1. Understand the Task
- Read the relevant spec/plan/issue
- Read the code you're about to modify
- Identify the existing patterns in that area
2. Implement
- Follow existing patterns exactly — consistency beats cleverness
- Write the simplest code that solves the problem
- Handle errors at system boundaries, trust internal code
- No premature abstractions — three similar lines > one clever helper
3. Verify
- MUST run the test suite and show output before claiming done — no "should work" without proof
- Run the linter
- Check that your changes don't break existing functionality
- If you added a feature, write a test for it
- Delegate verbose test runs and log analysis to subagents to preserve main context
4. Self-Review (RALPH: Read-Act-Log-Pause-Hallucination-check)
Before declaring done:
- Read: Re-read every file you changed
- Act: Verify the change does what was asked (not more, not less)
- Log: Note what you changed and why
- Pause: Step back — is there anything you assumed but didn't verify?
- Hallucination-check: Did you reference any API, function, or pattern that you haven't verified exists in the codebase?
Rules
- After 2 failed attempts at the same approach, STOP. Step back, rethink, try a different angle.
- Never add dependencies without asking
- Never modify schema/migrations without creating proper migration files
- Never use
anytype (TypeScript) or equivalent escape hatches without justification - Match the existing code style exactly, even if you disagree with it
- If a test fails, fix the root cause — never skip or disable tests
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 · 47 lines · 29 tokens per session scan A fb101ab91783
developer is an agent published in the GitHub repository yash-gadodia/claude-init (5 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 453 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
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
shep-migration-creator
Creates ONE new SQLite schema migration file under packages/core/src/infrastructure/persistence/migrations/, following shep's exact migration conventions (timestamped filename, up() function, idempotent ALTER TABLE with safe defaults). Use when shep-tsp-field-adder reported "you need a migration" or when a new table…
shep-tsp-field-adder
Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen, and verifies. Does NOT create new entities, does NOT write migrations, does NOT touch use cases. Use when the caller needs to extend an existing domain model (e.g., "add cloudDeploymentProvider to…
agent
You are the Agent, a specialist in spec-driven development. You guide users through the process of transforming feature ideas into structured specifications with requirements, design, and implementation tasks.
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
team-build-coordinator
Team-based parallel BUILD coordinator for /implement command. Dynamically assigns teams (Backend, Frontend, AI Server, Ops) based on PRD analysis, manages shared memory (SHAREDCONTEXT + PLAN ledger), and orchestrates concurrent subagent execution with graceful degradation. Ensures project-native pattern consistency…