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/backspace-shmackspace/claude-devkitWrote 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/backspace-shmackspace/claude-devkit/coder)<a href="https://agentmods.dev/agents/backspace-shmackspace/claude-devkit/coder"><img src="https://agentmods.dev/badge/agents/backspace-shmackspace/claude-devkit/coder/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/backspace-shmackspace/claude-devkit/coder"><img src="https://agentmods.dev/badge/agents/backspace-shmackspace/claude-devkit/coder.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.00011 | $0.00397 |
| Opus 5.5 | $0.00004 | $0.00159 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
coder 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 1mo 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
Inheritance
Base Agent: coder-base.md Base Version: 2.1.0 Specialist ID: coder Specialist Version: 1.0.0 Generated: 2026-02-24T22:01:43.084207
Tech Stack Override
REPLACES: [TECH_STACK_PLACEHOLDER] in base agent
- Language: Unknown
- Framework: None
- Testing: Manual testing
Project Patterns Reference
READ FIRST: ../../../CLAUDE.md
This project follows patterns documented in CLAUDE.md. Key sections to reference:
- Component/Module Structure
- State/Data Management
- API Integration
- Testing Strategy
- Quality Standards
Precedence: If conflict between this file and CLAUDE.md, CLAUDE.md wins (most current).
Quality Bar Extensions
Additions to base quality standards:
Code Quality
- Follow project naming conventions from CLAUDE.md
- Maintain consistency with existing patterns
- Write self-documenting code with clear variable/function names
Testing Requirements
- Unit tests for all new functions
- Integration tests for API endpoints/components
- Test coverage matches project standards (see CLAUDE.md)
Documentation
- Update CLAUDE.md when introducing new patterns
- Add comments for complex business logic
- Document public APIs and interfaces
Specialist Context Injection
{{SPECIALIST_CONTEXT}}:
- Read CLAUDE.md for project-specific patterns
- Reference existing code for consistency
- Apply tech stack best practices from base agent
Conflict Resolution
If patterns conflict between sources:
- CLAUDE.md takes precedence (most current project patterns)
- This specialist agent takes precedence over base (tech-specific)
- Base agent provides fallback defaults (universal standards)
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.
- 1mo ago First seen · 67 lines · 11 tokens per session scan A 7ee8f8bb9384
coder is an agent published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 397 once invoked, about $0.0000 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
artifact-sonnet
Use proactively for any HTML artifact page, new or revised, once its content is decided: a report, a consultation page, a dashboard. The page is written as a page SPEC (a .spec.md) and built; the agent never writes raw HTML for a new or revised page. Handoff: ONE page per brief, never two — a brief file with a named…
plugin-auditor
Launched by /aidex:aidex audit; not for direct use. Returns uninstall candidates by subagent cost vs usage.
reference-refuter
Launched by /aidex:reference step 5 (close gate); not for direct use. Returns a verdict per claim of a reference module.
web-researcher
Searches the web for a specific research query and returns a compressed finding with cohort-diverse citations and source-type annotations. Use when the parent recipe needs current-web information — especially fast-moving landscape/tooling topics where model priors can't be trusted.
regression-checker
Launched by /aidex:bugfix step 6; not for direct use. Returns whether the fix introduced regressions.
test-scout
Launched by /aidex:bugfix step 1; not for direct use. Returns the project's test framework and a regression-test approach.