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/growilabs/growi-mcp-server/spec-implgit clone --depth 1 https://github.com/growilabs/growi-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/growilabs/growi-mcp-server/spec-impl)<a href="https://agentmods.dev/commands/growilabs/growi-mcp-server/spec-impl"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/spec-impl.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.00007 | $0.00489 |
| Opus 5 | $0.00003 | $0.00244 |
| Sonnet 5 | $0.00001 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
spec-impl 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.
This is a copy
86% identical to spec-impl — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Implementation Task Executor
Parse Arguments
- Feature name:
$1 - Task numbers:
$2(optional)- Format: "1.1" (single task) or "1,2,3" (multiple tasks)
- If not provided: Execute all pending tasks
Validate
Check that tasks have been generated:
- Verify
.kiro/specs/$1/exists - Verify
.kiro/specs/$1/tasks.mdexists
If validation fails, inform user to complete tasks generation first.
Task Selection Logic
Parse task numbers from $2 (perform this in Slash Command before invoking Subagent):
- If
$2provided: Parse task numbers (e.g., "1.1", "1,2,3") - Otherwise: Read
.kiro/specs/$1/tasks.mdand find all unchecked tasks (- [ ])
Invoke Subagent
Delegate TDD implementation to spec-tdd-impl-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="spec-tdd-impl-agent",
description="Execute TDD implementation",
prompt="""
Feature: $1
Spec directory: .kiro/specs/$1/
Target tasks: {parsed task numbers or "all pending"}
File patterns to read:
- .kiro/specs/$1/*.{json,md}
- .kiro/steering/*.md
TDD Mode: strict (test-first)
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Task Execution
Execute specific task(s):
/kiro:spec-impl $1 1.1- Single task/kiro:spec-impl $1 1,2,3- Multiple tasks
Execute all pending:
/kiro:spec-impl $1- All unchecked tasks
Before Starting Implementation:
- IMPORTANT: Clear conversation history and free up context before running
/kiro:spec-impl - This applies when starting first task OR switching between tasks
- Fresh context ensures clean state and proper task focus
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 · 69 lines · 7 tokens per session scan A 7ccd8367edbc
spec-impl is a command published in the GitHub repository growilabs/growi-mcp-server (19 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 489 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to spec-impl, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
tdd-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
spec-impl
Execute spec tasks using TDD methodology.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
verification-repair
PitWay: Bounded, approve-before-edit correction after every task is done.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.