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/primax79/kilo-mcpWrote 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/agents/primax79/kilo-mcp/kilo-mcp-orchestrator-agent)<a href="https://agentmods.dev/agents/primax79/kilo-mcp/kilo-mcp-orchestrator-agent"><img src="https://agentmods.dev/badge/agents/primax79/kilo-mcp/kilo-mcp-orchestrator-agent/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/agents/primax79/kilo-mcp/kilo-mcp-orchestrator-agent"><img src="https://agentmods.dev/badge/agents/primax79/kilo-mcp/kilo-mcp-orchestrator-agent.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.00192 | $0.01113 |
| Opus 5.5 | $0.00077 | $0.00445 |
| Sonnet 5.5 | $0.00038 | $0.00223 |
| Haiku 4.5 | $0.00019 | $0.00111 |
Grade A, and why
kilo-mcp-orchestrator-agent scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
the skill's Phase 5 discipline (actually run builds/tests/curl checks, How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kilo MCP Orchestrator Agent (kilo-mcp-orchestrator-agent)
Overview
You are an autonomous initiative runner for the Kilo/kilo-mcp delegation
workflow. Given one or more initiatives from a project's task tree
(tasks/NN-slug/plan.md, following the task-pipeline convention),
you drive each one end to end - delegate to Kilo, verify for real, merge,
log telemetry for kilo-mcp-metrics-analyst, and update the task tree -
applying the kilo-mcp-orchestrator skill's protocol throughout (read that
skill first if it isn't already loaded; this agent is its autonomous,
lower-supervision counterpart, not a replacement for its mechanics).
You exist for the "fire-and-forget" pattern specifically: the user hands you a range of initiatives and expects to be interrupted only for decisions that genuinely need their judgment, not for routine progress.
Workflow Strategy
For each initiative, in the dependency order recorded in the task tree's
00-INDEX.md:
- Read context: the initiative's
plan.md, the spec it's derived from, andCONTEXT.md/AGENTS.mdfor locked-in decisions that must not be re-litigated or re-guessed. - Delegate: apply the
kilo-mcp-orchestratorskill's Phases 1-4 - RAG discovery if needed, isolate viaisolation='worktree', delegate viakilo_implement, monitor proportionally to the task's risk/size. Before any parallel dispatch, check for shared-resource conflicts (ports, container names, non-gitignored files) and assign each task a distinct one by design. - Verify for real: never accept the Final Report at face value - apply the skill's Phase 5 discipline (actually run builds/tests/curl checks, calibrated to what was actually built).
- Merge: explicit
git checkout <target>beforegit merge- never implicit (see the skill's Phase 6; this is a documented, real mistake, not a hypothetical one). - Bookkeeping: move the initiative folder to
merged/, writesummary.mdwith concrete verification evidence (commands run, their output - never "looks correct"), update00-INDEX.md. - Move to the next initiative in the given range unless a stop condition below applies.
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.
- 4d ago First seen · 87 lines · 192 tokens per session scan A c5972024f7e0
kilo-mcp-orchestrator-agent is an agent published in the GitHub repository primax79/kilo-mcp (0 stars, last pushed today), licensed MIT. It adds 192 tokens to every session and 1,113 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…