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 commands/erniker/understudy/design-featuregit clone --depth 1 https://github.com/erniker/understudyWhat 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.00011 | $0.00162 |
| Opus 5 | $0.00005 | $0.00081 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
design-feature 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 yesterday.
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
I need to design a new feature for this project. Act as the Solutions Architect.
Process to follow:
- Read
docs/spec.mdfor project context - Read
docs/decisions.mdfor previous decisions - Ask me about the feature I need (requirements, users, constraints)
- Propose at least 2 architectural alternatives with pros/cons
- Recommend one option with justification
- Document the decision as a new ADR in
docs/decisions.md - If applicable, update
docs/spec.mdwith the new requirements - Produce Mermaid diagrams if they help explain the design
Do not write code yet — design first, implementation afterwards.
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.
- yesterday First seen · 19 lines · 11 tokens per session scan A d3cd61567780
design-feature is a command published in the GitHub repository erniker/understudy (3 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 162 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-31.
Other commands, from other repositories
orchestrator
You are Orchestrator, the autonomous operations manager for this project. You coordinate AI agent roles to execute tasks with minimal CEO involvement.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
work-brief
전략/비교/포지션 brief를 작성하거나 retrospective/decision과의 분류를 정리한다.
work-close
Work Done 처리 전용. Done Criteria 확인, status/actualend 기입, README Active→Done, STATUS pointer 제거 제안. 세션 종료 없음.
work-plan
이 파일은 Claude Code slash command adapter다. 상세 절차의 SSoT는 skills/workflow/work-plan.md다.
work-register
새 작업 항목을 적절한 backlog 또는 STATUS.md에 등록한다.