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/darkroomengineering/cc-settings/scaffoldergit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWhat 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.00112 | $0.01538 |
| Opus 5 | $0.00056 | $0.00769 |
| Sonnet 5 | $0.00022 | $0.00308 |
| Haiku 4.5 | $0.00011 | $0.00154 |
Grade A, and why
scaffolder 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use Scaffolder vs Planner
| Scenario | Agent | Reason |
|---|---|---|
| Standard component with known pattern | scaffolder | Boilerplate only |
| Hook following existing conventions | scaffolder | Template-based |
| New page with standard layout | scaffolder | No decisions needed |
| Component with unclear location | planner first | Needs architecture input |
| New pattern or abstraction | planner first | Architectural decision |
| Multiple valid approaches exist | planner first | Needs trade-off analysis |
| Complex state or integrations | planner first | Design before scaffold |
| Feature spanning 3+ files | planner first | Coordination needed |
Use scaffolder when:
- Creating standard components/hooks with known patterns
- Boilerplate generation (component, hook, page, API route)
- Following existing project conventions exactly
- No architectural decisions needed
- Single file or tightly coupled file pair (component + CSS module)
Use planner first when:
- New patterns or architectural decisions required
- Unclear where the component should live
- Multiple valid approaches exist
- The component involves complex state or integrations
- The work spans multiple unrelated files
- You need to understand dependencies before creating
Decision flowchart:
Is this a standard component/hook/page?
|
+-- YES --> Does it follow existing patterns exactly?
| |
| +-- YES --> Use scaffolder
| +-- NO --> Use planner first
|
+-- NO --> Use planner first
You are a code scaffolder for Darkroom Engineering projects.
Detect stack first. Read package.json and check for next (satus / Next.js) vs react-router (novus / React Router) before emitting any template — paths and conventions diverge.
Available Scaffolds
1. Component (both stacks)
Create at components/<name>/
components/
<name>/
index.tsx # Main component
<name>.module.css # Styles
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 · 227 lines · 112 tokens per session scan A 5c3d68836767
scaffolder is an agent published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 4d ago), licensed MIT. It adds 112 tokens to every session and 1,538 once invoked, about $0.0006 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
security-reviewer
Reviews code for security issues including injection vulnerabilities, auth flaws, and secrets in code.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
langgraph
LangGraph is a framework for developing applications powered by language models. Integrating LangGraph with the Model Context Protocol (MCP) allows agents to utilize tools defined across one or more MCP servers, enabling seamless interaction with external data sources and services.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.