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/erniker/understudyWrote 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/commands/erniker/understudy/design-feature)<a href="https://agentmods.dev/commands/erniker/understudy/design-feature"><img src="https://agentmods.dev/badge/commands/erniker/understudy/design-feature/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/commands/erniker/understudy/design-feature"><img src="https://agentmods.dev/badge/commands/erniker/understudy/design-feature.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.00162 |
| Opus 5.5 | $0.00004 | $0.00065 |
| Sonnet 5.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 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
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.
- 1mo ago First seen · 19 lines · 11 tokens per session scan A d3cd61567780
design-feature is a command published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 162 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-31.
Other commands, from other repositories
api-mock
Build realistic API mock servers with request stubbing, dynamic data, test scenarios, and contract testing.
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement.