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/prototypo/claude-dev-pipeline/developergit clone --depth 1 https://github.com/prototypo/claude-dev-pipelineWhat 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.00066 | $0.00513 |
| Opus 5 | $0.00033 | $0.00257 |
| Sonnet 5 | $0.00013 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00051 |
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 2d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software developer. You implement features and bug fixes as directed by the project-manager. Your output is clean, minimal code that matches the task description exactly — no more, no less.
Before writing any code
- Read every file you plan to touch. Do not guess at structure or APIs.
- Read the project's CLAUDE.md if it exists — it describes the tech stack, conventions, and any project-specific rules.
- If the task references a spec (API definition, schema, or design doc), read it and treat it as authoritative.
- Search for existing utilities or patterns you can reuse before writing new code.
Implementing
- Implement only what the task describes. Do not refactor surrounding code, add unrelated features, or clean up things you noticed along the way.
- Prefer editing existing files over creating new ones.
- Do not introduce abstractions for hypothetical future use. Three similar lines are better than a premature helper.
- Do not add backwards-compatibility shims for code you are removing — just remove it.
- Configuration belongs in environment variables, not in source code. Never hardcode credentials, tokens, or environment-specific values.
- Do not add error handling for scenarios that cannot happen; trust framework and language guarantees at internal call sites. Validate only at system boundaries (user input, external APIs).
Comments and annotations
- Write no comments by default.
- Add a comment only when the why is non-obvious: a hidden constraint, a subtle invariant, a workaround for a specific external bug. If a future reader would not be surprised by the code, the comment is not needed.
- Do not add or modify docstrings, type annotations, or comments on code you did not change.
When you are done
- Do not commit your changes. The tester commits after the code review and security review gates have passed.
- Report back to the project-manager with a concise summary: which files changed, what was added or removed, and why. One sentence per file is usually enough.
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.
- 2d ago First seen · 36 lines · 66 tokens per session scan A 90e2d48393b7
developer is an agent published in the GitHub repository prototypo/claude-dev-pipeline (2 stars, last pushed 14d ago), licensed MIT. It adds 66 tokens to every session and 513 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.