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 instructions/komluk/scaffolding/claude-mdgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/instructions/komluk/scaffolding/claude-md)<a href="https://agentmods.dev/instructions/komluk/scaffolding/claude-md"><img src="https://agentmods.dev/badge/instructions/komluk/scaffolding/claude-md.svg" alt="Measured on agentmods" 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 | $0.01120 | $0.01120 |
| Opus 5 | $0.00560 | $0.00560 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
scaffolding CLAUDE.md 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol
BEHAVIOR:
- Auto-route - Treat engineering requests as tasks. Route to the right agent.
- No confirmation - For real work, don't ask. Just delegate.
- Concise responses - Short status. No verbose explanations unless asked.
Delegate via: Task(subagent_type="scaffolding:<agent>", prompt="...", description="...")
Response format: [Agent: name] Task -> Result (1-2 lines)
Agents (13)
| Agent | Tier | When to Use |
|---|---|---|
| scaffolding:analyst | opus | Ambiguous requests, requirements, scope assessment, feasibility, proposal writing |
| scaffolding:architect | opus | System design, API design, implementation planning, multi-file refactoring, agent orchestration |
| scaffolding:researcher | sonnet | New API integration, library questions, best practices (gate: score >= 80) |
| scaffolding:developer | sonnet | Implementation, bug fixes, features, tests, UI/styling (gate: validation passes) |
| scaffolding:debugger | opus | Bug reports, unexpected behavior, errors |
| scaffolding:reviewer | sonnet | After code changes, security analysis, threat modeling (gate: no criticals) |
| scaffolding:optimizer | sonnet | Performance issues, database design, schema, migrations, queries |
| scaffolding:prompt-engineer | sonnet | System prompts, prompt templates, guardrail rules, prompt evals, LLM-judge rubrics, injection defense |
| scaffolding:mcp-builder | sonnet | Build/modify MCP servers, tool schema design, stdio/http transport, MCP auth/secret launchers |
| scaffolding:tech-writer | haiku | Documentation, CHANGELOG updates |
| scaffolding:devops | sonnet | CI/CD, deployment, infrastructure |
| scaffolding:gitops | haiku | Branch management, conflict resolution, git history, worktree recovery, push to remote |
| scaffolding:coordinator | sonnet | Analyzes tasks, decomposes into agent step sequences for dynamic execution |
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.
- 5d ago First seen · 82 lines · 1,120 tokens per session scan A c5d15c797df8
scaffolding CLAUDE.md is an instructions file published in the GitHub repository komluk/scaffolding (15 stars, last pushed 29d ago), licensed MIT. It adds 1,120 tokens to every session, about $0.0056 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 instructions, from other repositories
markifact-mcp GEMINI.md
Instructions for markifact/markifact-mcp, covering markifact, the 8 tools, discover → inspect → run, connection vs account and reporting workflow.
Version-Sentinel CLAUDE.md
Instructions for KSEGIT/Version-Sentinel, covering version sentinel, project structure, supported ecosystems, how it works and prerequisites.
Version-Sentinel GEMINI.md
Instructions for KSEGIT/Version-Sentinel, covering version-sentinel (gemini cli extension), how it works, intentional pins, auditing drift and escape hatch.
Looptimal CLAUDE.md
Instructions for Renn-Labs/Looptimal, covering looptimal — repo guidance for ai agents, build journal — capture the concepts, not the changelog and — .
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
superpowers-graph CLAUDE.md
Claude Code instructions for RonMizrahi/superpowers-graph, covering superpowers-graph — repository guide, sources of truth, changing the graph — the eval ships with the change and rules that are not obvious from the code.