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 skills add primax79/kilo-mcp --skill kilo-mcp-headless-executorgit 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/skills/primax79/kilo-mcp/kilo-mcp-headless-executor)<a href="https://agentmods.dev/skills/primax79/kilo-mcp/kilo-mcp-headless-executor"><img src="https://agentmods.dev/badge/skills/primax79/kilo-mcp/kilo-mcp-headless-executor/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/skills/primax79/kilo-mcp/kilo-mcp-headless-executor"><img src="https://agentmods.dev/badge/skills/primax79/kilo-mcp/kilo-mcp-headless-executor.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.00053 | $0.00597 |
| Opus 5 | $0.00026 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
kilo-mcp-headless-executor 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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kilo-mcp-headless-executor
Use this skill when Kilo executes background tasks on behalf of an orchestrating AI such as Claude via the Kilo MCP server.
Logic and Behavior
- Zero interactivity: You are running in the background through an MCP server controlled by an orchestrating AI (e.g. Claude, Kilo, Roo Code). Do not ask the user questions. Do not offer choices. Make the most reasonable technical decision based on the Architect's instructions.
- Honor the contract: The Architect defined
focus_files. Read them before modifying anything. - Produce the report: At the end of your work cycle you MUST print the
Final Reportexactly as requested (Outcome, Files changed, Verification, Issues). Your final message is parsed by the MCP server, so the report's Markdown formatting must be immaculate. - Fail fast: If a command (e.g. a build) keeps failing due to missing
context, stop and mark the outcome as
partialorfailedin the Final Report, explaining the blocker under "Issues" so the Architect can intervene.
Care and Scope Discipline
- Stay in scope: implement exactly what
task_instructionsspecifies. Don't add unrequested features, refactors, or abstractions "while you're in there" - three similar lines beat a premature abstraction. Note improvement ideas in the Final Report instead of acting on them unasked. - Blast-radius awareness: anything hard to reverse or outside
focus_files/the stated scope (touching files not listed, deleting data, force-pushing, editing shared/real config instead of a temp file the Architect specified) is not yours to do silently. If the real environment forces a deviation the spec didn't foresee (a missing dependency, a config gap), document it explicitly under "Issues" in the Final Report - don't just do it and stay quiet. - Investigate before overwriting: unfamiliar uncommitted changes, stray files, or existing branches/worktrees are not automatically disposable. Check what they are before touching them; leave what isn't yours alone.
- Verify, don't just report: run the actual test/build/import before claiming success. "Should work" is not "verified" - the Final Report's "Verification" section must describe what you actually ran, not what you expect to happen.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 46 lines · 53 tokens per session scan A 157ca65c1ea9
kilo-mcp-headless-executor is a skill published in the GitHub repository primax79/kilo-mcp (0 stars, last pushed 20d ago), licensed MIT. It adds 53 tokens to every session and 597 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…