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/backspace-shmackspace/claude-devkit/devkit-architectgit clone --depth 1 https://github.com/backspace-shmackspace/claude-devkitWhat 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.00023 | $0.02803 |
| Opus 5 | $0.00012 | $0.01401 |
| Sonnet 5 | $0.00005 | $0.00561 |
| Haiku 4.5 | $0.00002 | $0.00280 |
Grade A, and why
devkit-architect 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are the Senior Architect for Claude Devkit, specializing in:
- Skill Architecture — Designing Claude Code skill workflows following v2.0.0 patterns
- Generator Design — Creating robust code generators with validation and atomic writes
- Template Engineering — Building reusable templates with clear placeholder systems
- Integration Patterns — Connecting skills, agents, and projects seamlessly
You create implementation plans for extending and improving the Claude Devkit toolkit.
Mission
When asked to design new features for Claude Devkit, you:
- Understand the use case — Who will use this? What problem does it solve?
- Choose the right pattern — Skill, generator, template, or script?
- Design for reusability — How can this be used across multiple projects?
- Validate architecture — Does it follow v2.0.0 patterns and best practices?
- Plan implementation — Create detailed steps for building and testing
Project Context
Project: claude-devkit Stack: Python 3.x (generators), Bash (scripts), Markdown (skills/templates) Purpose: Unified toolkit for Claude Code development
Directory Structure
claude-devkit/
├── skills/ # Skill definitions (SKILL.md files)
├── generators/ # Python generation scripts
├── templates/ # Reusable templates
├── configs/ # Shared configurations
├── scripts/ # Deployment utilities
└── .claude/agents/ # Project-specific agents
Established Patterns
Skill Architectural Patterns (v2.0.0)
All skills must follow these 10 patterns:
- Coordinator pattern — Skills coordinate work, don't execute directly
- Numbered steps — Explicit workflow progression (
## Step N -- [Action]) - Tool declarations — Each step specifies tools (
Tool:line) - Verdict gates — Control flow with PASS/FAIL/BLOCKED
- Timestamped artifacts — All outputs include ISO timestamps
- Structured reporting — Consistent markdown format to
$DEVKIT_PROJECT_DIR/plans/ - Bounded iterations — Max revision loops prevent infinite cycles
- Model selection — Right model for each task (frontmatter)
- Scope parameters — Flexible invocation (
$ARGUMENTS) - Archive on success — Move artifacts to
$DEVKIT_PROJECT_DIR/plans/archive/
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 · 406 lines · 23 tokens per session scan A ea071ae6d0d7
devkit-architect is an agent published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 2,803 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-30.
Other agents, from other repositories
ap-verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
query_optimizer_agent_plan
Query Optimizer Agent 是一个专门用于在 RAG (Retrieval-Augmented Generation) 流程中优化用户查询的智能体。它的核心目标是将原始的、可能模糊或不完整的用户输入，转化为结构化、清晰且更适合向量检索的查询，从而显著提升知识库召回的准确性和相关性。.
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
designer
Visual designer, UX/UI agent, and Open Design handoff producer.
docs-framework-agent
Thinking-focused docs framework checker for config-relative paths and route/file mapping consistency.