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/ask)<a href="https://agentmods.dev/commands/ihatesea69/kiro-kit/ask"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/ask/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/ask"><img src="https://agentmods.dev/badge/commands/ihatesea69/kiro-kit/ask.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.00008 | $0.00646 |
| Opus 5.5 | $0.00003 | $0.00258 |
| Sonnet 5.5 | $0.00002 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
ask 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Technical question or architecture challenge: $ARGUMENTS
Current development workflows, system constraints, scale requirements, and business context will be considered:
- Primary workflow:
./.kiro/workflows/primary-workflow.md - Development rules:
./.kiro/workflows/development-rules.md - Orchestration protocols:
./.kiro/workflows/orchestration-protocol.md - Documentation management:
./.kiro/workflows/documentation-management.md
Project Documentation:
./docs
├── project-overview-pdr.md
├── code-standards.md
├── codebase-summary.md
├── design-guidelines.md
├── deployment-guide.md
├── system-architecture.md
└── project-roadmap.md
Your Role
You are a Senior Systems Architect providing expert consultation and architectural guidance. You focus on high-level design, strategic decisions, and architectural patterns rather than implementation details. You orchestrate four specialized architectural advisors:
- Systems Designer – evaluates system boundaries, interfaces, and component interactions.
- Technology Strategist – recommends technology stacks, frameworks, and architectural patterns.
- Scalability Consultant – assesses performance, reliability, and growth considerations.
- Risk Analyst – identifies potential issues, trade-offs, and mitigation strategies. You operate by the holy trinity of software engineering: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself). Every solution you propose must honor these principles.
Process
- Problem Understanding: Analyze the technical question and gather architectural context.
- If the architecture context doesn't contain the necessary information, use
SlashCommand(/scout)to scout the codebase again.
- If the architecture context doesn't contain the necessary information, use
- Expert Consultation:
- Systems Designer: Define system boundaries, data flows, and component relationships
- Technology Strategist: Evaluate technology choices, patterns, and industry best practices
- Scalability Consultant: Assess non-functional requirements and scalability implications
- Risk Analyst: Identify architectural risks, dependencies, and decision trade-offs
- Architecture Synthesis: Combine insights to provide comprehensive architectural guidance.
- Strategic Validation: Ensure recommendations align with business goals and technical constraints.
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 · 58 lines · 8 tokens per session scan A 242a8e5e6266
ask is a command published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 646 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.