Borrowing it
Nothing to install: this file belongs to kavo-labs/kavo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kavo-labs/kavo/main/.claude/commands/implement.mdgit clone --depth 1 https://github.com/kavo-labs/kavoWrote 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/kavo-labs/kavo/implement)<a href="https://agentmods.dev/commands/kavo-labs/kavo/implement"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/implement/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/kavo-labs/kavo/implement"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/implement.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.00021 | $0.01314 |
| Opus 5.5 | $0.00008 | $0.00526 |
| Sonnet 5.5 | $0.00004 | $0.00263 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
implement 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git rev-parse --abbrev-ref HEAD - Working tree: !
git status --short - Recent commits: !
git log --oneline -5
Your task
Arguments: $ARGUMENTS — the first token is the issue number; anything after it is extra instructions or corrections to fold in during implementation.
-
Preflight. If no issue number was given, stop and ask for one. If there is no GitHub remote, stop and say so.
-
Read the issue in full:
gh issue view <n> --json title,body,labels,comments. Restate its goal and acceptance criteria to yourself so the implementation is judged against them, not against a guess. If the issue is too vague to implement — missing acceptance criteria, an ambiguous design choice with no default the codebase implies — stop and ask rather than guessing; do not silently narrow the scope. -
Locate the seam before writing code. Kavo is built out of swappable seams (
packages/core/src/engine/kavo-engine.ts's Template Method: operation resolution → config resolution → DTO resolution → deserialization → query resolution → handler execution → response mapping → serialization). Most changes are "add or modify a seam", not "add a branch" — find the existing seam before proposing a new mechanism. Check the invariants and ADRs your change touches (registry-driven operations, ADR-0006; decoration-time routes, ADR-0012; the explicit named barrel, ADR-0010; the composition root freezing aftercreateCrud) and read the governing ADR indocs/internals/adr/before changing behavior it covers. Follow the naming conventions inCLAUDE.md— they are normative. -
Create the branch, in an isolated worktree. Follow the
conventionsskill to derive<type>from the issue's label. CallEnterWorktreewithname: "<issue-number>-<short-slug>"to create a fresh worktree — branched off up-to-datemain— and switch the session into it, then rename the branch to match the convention:git branch -m <type>/<issue-number>-<short-slug>. Implementing in a worktree keeps this work off the branch the user's editor has open.
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 · 114 lines · 21 tokens per session scan A 29816e389e4c
implement is a command published in the GitHub repository kavo-labs/kavo (17 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,314 once invoked, about $0.0001 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-09-02.
Other commands, from other repositories
read
Read data from a Google Sheets range.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
end
End the current collaboration session and release all claims.
commit
Based on the above changes, create a single git commit.