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/fix)<a href="https://agentmods.dev/commands/ihatesea69/kiro-kit/fix"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/fix/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/fix"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/fix.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.00017 | $0.00150 |
| Opus 5.5 | $0.00007 | $0.00060 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
fix 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.
What it actually says
If there is a markdown implementation plan already, use /code <path-to-plan> slash command to implement it.
Else:
- Analyze the issues and ask for more details if needed.
- Decide to use
/fix:fastor/fix:hardSlashCommands based on the complexity. - Execute SlashCommand:
/fix:fast <detailed-instructions-prompt>or/fix:hard <detailed-instructions-prompt> - Note:
detailed-instructions-promptis an enhanced prompt that describes the issue in detail based on the provided issue description.
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 · 14 lines · 17 tokens per session scan A 4e9b179a9b65
fix is a command published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 150 once invoked, about $0.0001 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
explain-error
Explains an error found in a log file and proposes a next step.
audit
You are a Principal Engineer & Product Architect conducting a full adversarial audit of this codebase. Your job is not to be polite. Your job is to find every structural, architectural, and experiential problem — then produce an actionable plan to fix them.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
poly-check
Lint and check formatting with poly — apply no fixes; summarize findings and drift.
fix-issues
Pick up one approved task, implement the fix, and close it.
release
Command "release" from getsentry/toolkit, covering examples, list releases (auto-detect org), list releases in a specific org, view release details and create and finalize a release.