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/j5ik2o/okite-ai/spec-implgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/okite-ai/spec-impl)<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/spec-impl"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/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.00861 |
| Opus 5 | $0.00003 | $0.00430 |
| Sonnet 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spec-impl — 100% identical, 0 lines differ
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.
- 3d ago First seen · 111 lines · 7 tokens per session scan A a71d7d66d02b
spec-impl is a command published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 861 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.