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 agents/rune-kit/rune/cookgit clone --depth 1 https://github.com/Rune-kit/runeWhat 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.00046 | $0.00676 |
| Opus 5 | $0.00023 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
cook 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cook skill — Rune's primary implementation orchestrator.
Step 0 — Prerequisite Check (BEFORE starting work)
- Plan exists? Check for
.rune/plan-*.mdor approved plan in conversation. If non-trivial task (3+ files or significant logic) and NO plan → invokerune:planfirst, wait for user approval, then return here. - Codebase scanned? Check if scout has run. If no codebase context → invoke
rune:scoutto gather structure before Phase 1. - Contract loaded? Check for
.rune/contract.md. If exists, load and enforce throughout. - Resume check? Check for
.rune/plan-*-phase*.mdor.continue-here.md→ resume from last checkpoint.
Only proceed to Phase 1 after Step 0 is satisfied.
Quick Reference
8-Phase Workflow (scaled by rigor assessment):
- Understand — scout codebase, run BA for requirements, clarify scope (max 2 questions)
- Plan — create implementation plan; user MUST approve before proceeding
- Test (RED) — write failing tests first (happy path + edge cases)
- Implement (GREEN) — code to pass tests; max 3 debug loops, 1 replan
- Quality — Stage 1: preflight + sentinel (parallel) → Stage 2: review + completion-gate (parallel)
- Verify — lint + types + tests + build ALL green
- Commit — semantic git commit via git skill
- Bridge — save decisions, progress, conventions for next session
Rigor Levels (auto-assessed from risk signals):
- Nano (0 risk) → DO → VERIFY → DONE (≤3 steps, no logic)
- Fast (1-2) → Understand → Implement → Verify → Commit
- Standard (3-5) → All phases except adversary
- Full (6-8) → All phases including adversary red-team
- Critical (9+) → All phases + sentinel@opus + adversary
Hard Gates:
- Scout BEFORE planning — no guessing codebase structure
- User MUST approve plan before writing tests
- Tests MUST fail before implementation (TDD red-first)
- ALL tests green before commit — zero exceptions
- 5+ consecutive reads without a write = STUCK → act or report BLOCKED
- Contract violations (
.rune/contract.md) are non-negotiable
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.
- 2d ago First seen · 49 lines · 46 tokens per session scan A b7ac010c2a1e
cook is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 16d ago), licensed MIT. It adds 46 tokens to every session and 676 once invoked, about $0.0002 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 agents, from other repositories
polymath
Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.
insistir-reviewer
Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …
insistir-researcher
Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.
insistir-learnings-researcher
Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.
insistir-worker
Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.
askit-explorer
Surveys a repository broadly and reports a structural map of its components and layout. Use when delegating broad read-only exploration - the bounded discovery role for answering what exists and how a repo is organized.