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/sawadari/requirements-mcp-server/testgit clone --depth 1 https://github.com/sawadari/requirements-mcp-serverWrote 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/sawadari/requirements-mcp-server/test)<a href="https://agentmods.dev/commands/sawadari/requirements-mcp-server/test"><img src="https://agentmods.dev/badge/commands/sawadari/requirements-mcp-server/test.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.00011 | $0.00401 |
| Opus 5 | $0.00005 | $0.00200 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
test 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 4d 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
テスト実行
プロジェクト全体のTypeScriptコンパイルとテストスイートを実行します。
実行内容
-
TypeScript型チェック
npm run typecheck- Strict mode有効
- 全11ファイル検証
- エラー0件が目標
-
Vitestテストスイート
npm test- CoordinatorAgentテスト
- DAG構築テスト
- 循環依存検出テスト
期待される結果
✅ TypeScript: エラー0件 ✅ Tests: 6/6 passing ✅ Duration: <1秒
テスト対象
tests/coordinator.test.ts- Task decomposition
- DAG construction
- Circular dependency detection
- Agent assignment
- Execution plan
カバレッジ確認
npm run test:coverage
失敗時の対処
TypeScriptエラー
# エラー詳細確認
npm run typecheck
# 型定義確認
cat agents/types/index.ts
テスト失敗
# 詳細モードで実行
npm test -- --reporter=verbose
# 特定のテストのみ
npm test -- tests/coordinator.test.ts
CI/CD統合
GitHub Actionsで自動実行されます：
- name: Run TypeScript compilation check
run: npm run typecheck
- name: Run tests
run: npm test
実行完了後、全テストが合格していることを確認してください。
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.
- 4d ago First seen · 83 lines · 11 tokens per session scan A 1dc66719a65a
test is a command published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 401 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
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.