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/kavo-labs/kavo/listgit 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/list)<a href="https://agentmods.dev/commands/kavo-labs/kavo/list"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/list.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00300 |
| Opus 5 | $0.00006 | $0.00150 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
list 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
Context
- Repo: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "NO REMOTE" - Issues: !
gh issue list --state open --limit 50 2>/dev/null || echo "unavailable"
Your task
Filter, if given: $ARGUMENTS. The context above already covers the
default (open, unfiltered) case — only re-run gh issue list if a filter was
given:
- a label (e.g.
area:core,status:ready) —gh issue list --label "<label>" closed—gh issue list --state closed
If the repo line says NO REMOTE, stop and say this repo has no GitHub remote.
Show the issues as a table: number, title, labels, status (ready /
blocked / no status label — most issues will have no status label, since
labeling one status:ready is a manual, deliberate step). Group
status:ready issues first, then status:blocked, then unlabeled-status
issues last. Keep it terse — this is a lookup, not a report.
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 · 28 lines · 13 tokens per session scan A 21f8cc30454f
list is a command published in the GitHub repository kavo-labs/kavo (12 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 300 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-09-02.
Other commands, from other repositories
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo-blog
Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
start
Runs a project that has already been compiled with vendure build.
pre-commit
Before running the checklist, run git fetch origin. If the current branch is behind origin/master, stop and rebase before proceeding.