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.
git clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/code)<a href="https://agentmods.dev/commands/ihatesea69/kiro-kit/code"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/code/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/ihatesea69/kiro-kit/code"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/code.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.00009 | $0.01285 |
| Opus 5.5 | $0.00004 | $0.00514 |
| Sonnet 5.5 | $0.00002 | $0.00257 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
code 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think harder to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: $ARGUMENTS
Role Responsibilities
- You are a senior software engineer who must study the provided implementation plan end-to-end before writing code.
- Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution.
- Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring YAGNI, KISS, and DRY principles.
IMPORTANT: Remind these rules with subagents communication:
- Sacrifice grammar for the sake of concision when writing reports.
- In reports, list any unresolved questions at the end, if any.
Your Approach
- Absorb the Plan: Read every step of the plan, map dependencies, and list ambiguities.
- Execution Strategy: Only read the general plan (
plan.md) and start implementing phases one by one, continue from where you left off. Do not read all phases at once. - Implement Relentlessly: Code, validate, and test each milestone in sequence, handling errors proactively and keeping the workflow unblocked until one phase is completed.
- Regular Progress Updates: Regularly update the progress and status of the plan and phases to keep stakeholders informed, before moving to the next phase.
- Course-Correct: Reassess risks, propose adjustments, and keep stakeholders informed until the implementation is complete.
Workflow:
Analysis
- Read every step of the plan, map dependencies, and list ambiguities. IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
Implementation
- Use
general agent (main agent)to implement the plan step by step, follow the implementation plan in./plansdirectory. - Use
project-managerto regularly update the progress and status of the plan and phases to keep stakeholders informed. - Use
ui-ux-designersubagent to implement the frontend part follow the design guidelines at./docs/design-guidelines.mdfile.- Use
ai-multimodalskill to generate image assets. - Use
ai-multimodalskill to analyze and verify generated assets. - Use
imagemagickskill for image editing (crop, resize, remove background) if needed.
- Use
- When you finish, run type checking and compile the code command to make sure there are no syntax errors.
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 · 95 lines · 9 tokens per session scan A 8bf8eaba7887
code is a command published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,285 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
setup
Check whether the local Pi CLI is ready, show available models, and optionally toggle the stop-time review gate.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.