Borrowing it
Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. 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/j5ik2o/event-store-adapter-js/main/.claude/commands/kiro/spec-impl.mdgit clone --depth 1 https://github.com/j5ik2o/event-store-adapter-jsWrote 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/j5ik2o/event-store-adapter-js/spec-impl)<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/spec-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/spec-impl/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/j5ik2o/event-store-adapter-js/spec-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/spec-impl.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.00007 | $0.00861 |
| Opus 5.5 | $0.00003 | $0.00344 |
| Sonnet 5.5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00001 | $0.00086 |
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 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.
This is a copy
100% identical to spec-impl — 0 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Task Executor
<background_information>
- Mission: Execute implementation tasks using Test-Driven Development methodology based on approved specifications
- Success Criteria:
- All tests written before implementation code
- Code passes all tests with no regressions
- Tasks marked as completed in tasks.md
- Implementation aligns with design and requirements </background_information>
Execution Steps
Step 1: Load Context
Read all necessary context:
.kiro/specs/$1/spec.json,requirements.md,design.md,tasks.md- Entire
.kiro/steering/directory for complete project memory
Validate approvals:
- Verify tasks are approved in spec.json (stop if not, see Safety & Fallback)
Step 2: Select Tasks
Determine which tasks to execute:
- If
$2provided: Execute specified task numbers (e.g., "1.1" or "1,2,3") - Otherwise: Execute all pending tasks (unchecked
- [ ]in tasks.md)
Step 3: Execute with TDD
For each selected task, follow Kent Beck's TDD cycle:
-
RED - Write Failing Test:
- Write test for the next small piece of functionality
- Test should fail (code doesn't exist yet)
- Use descriptive test names
-
GREEN - Write Minimal Code:
- Implement simplest solution to make test pass
- Focus only on making THIS test pass
- Avoid over-engineering
-
REFACTOR - Clean Up:
- Improve code structure and readability
- Remove duplication
- Apply design patterns where appropriate
- Ensure all tests still pass after refactoring
-
VERIFY - Validate Quality:
- All tests pass (new and existing)
- No regressions in existing functionality
- Code coverage maintained or improved
-
MARK COMPLETE:
- Update checkbox from
- [ ]to- [x]in tasks.md
- Update checkbox from
Critical Constraints
- TDD Mandatory: Tests MUST be written before implementation code
- Task Scope: Implement only what the specific task requires
- Test Coverage: All new code must have tests
- No Regressions: Existing tests must continue to pass
- Design Alignment: Implementation must follow design.md specifications
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 · 111 lines · 7 tokens per session scan A a71d7d66d02b
spec-impl is a command published in the GitHub repository j5ik2o/event-store-adapter-js (25 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 861 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-impl, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
generate-widget
Génération Widget Flutter avec Tests.
api-endpoint
Création Endpoint API Platform.
a11y-audit
Audit Accessibilité WCAG 2.2 AAA.
check-testing
Angular Test Coverage and Quality Analysis.
pre-merge-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.