Borrowing it
Nothing to install: this file belongs to mingyo186/instrument-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mingyo186/instrument-mcp/master/.claude/commands/add-scenario.mdgit clone --depth 1 https://github.com/mingyo186/instrument-mcpWrote 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/mingyo186/instrument-mcp/add-scenario)<a href="https://agentmods.dev/commands/mingyo186/instrument-mcp/add-scenario"><img src="https://agentmods.dev/badge/commands/mingyo186/instrument-mcp/add-scenario/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/mingyo186/instrument-mcp/add-scenario"><img src="https://agentmods.dev/badge/commands/mingyo186/instrument-mcp/add-scenario.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.00000 | $0.00193 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
add-scenario 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 8d 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
새로운 사용 시나리오를 구현합니다.
입력
- 시나리오 설명: $ARGUMENTS
작업 절차
- 시나리오에 필요한 Tool 목록 파악
- 부족한 Tool이 있으면
/add-tool커맨드로 추가 - Mock 드라이버에 시나리오에 맞는 샘플 데이터 추가 (
src/mock/sample_data/) - 시나리오 테스트 작성 (Tool 호출 순서를 검증하는 통합 테스트)
- 테스트 실행 확인
예시 시나리오
- 전원 레일 디버깅: scope_connect → scope_capture → scope_analyze_ripple
- 보드 초기 검증: psu_set_output → psu_enable → dmm_measure (여러 레일) → logic_decode_uart
- SPI 통신 진단: logic_capture → logic_decode_spi → logic_check_timing
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.
- 8d ago First seen · 17 lines · 0 tokens per session scan A 54eca92c3e3e
add-scenario is a command published in the GitHub repository mingyo186/instrument-mcp (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 193 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.