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/ihatesea69/kiro-kit/use-mcpgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00012 | $0.00386 |
| Opus 5 | $0.00006 | $0.00193 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
use-mcp 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.
What it actually says
Execute MCP operations via Gemini CLI to preserve context budget.
Execution Steps
-
Execute task via Gemini CLI (using stdin pipe for MCP support):
# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init) echo "$ARGUMENTS. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash -
Fallback to mcp-manager subagent (if Gemini CLI unavailable):
- Use
mcp-managersubagent to discover and execute tools - If the subagent got issues with the scripts of
mcp-managementskill, usemcp-builderskill to fix them - DO NOT create ANY new scripts
- The subagent can only use MCP tools if any to achieve this task
- If the subagent can't find any suitable tools, just report it back to the main agent to move on to the next step
- Use
Important Notes
- MUST use stdin piping - the deprecated
-pflag skips MCP initialization - Use
-yflag to auto-approve tool execution - GEMINI.md auto-loaded: Gemini CLI automatically loads
GEMINI.mdfrom project root, enforcing JSON-only response format - Parseable output: Responses are structured JSON:
{"server":"name","tool":"name","success":true,"result":<data>,"error":null}
Anti-Pattern (DO NOT USE)
# BROKEN - deprecated -p flag skips MCP server connections!
gemini -y -m gemini-2.5-flash -p "..."
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 · 36 lines · 12 tokens per session scan A 4b7d898e1309
use-mcp is a command published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 14d ago), licensed MIT. It adds 12 tokens to every session and 386 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
phase-0-discovery
Understand the organization, its industry, its constraints, and its goals before touching any code. Present these questions conversationally, not as a checklist. Follow up based on answers.
phase-3-target-architecture
Propose the future-state architecture based on Phases 0-2. Expect multiple revision cycles.
phase-4-modernization-plan
Turn the target architecture into an actionable, phased implementation plan.
phase-1-codebase-analysis
Read the actual source code and produce a factual technical assessment of each application. No recommendations yet — purely diagnostic.
phase-5-supporting-docs
Produce documents for stakeholders beyond the technical team.
phase-2-pain-points
Understand what the current system fails to do from the users' perspective. The codebase tells you what the system does. The users tell you what it doesn't do.