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/issuegit 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/issue)<a href="https://agentmods.dev/commands/kavo-labs/kavo/issue"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/issue.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.00016 | $0.00933 |
| Opus 5 | $0.00008 | $0.00466 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
issue 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a GitHub issue for: $ARGUMENTS
Context
- Repo: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "NO REMOTE" - Existing labels: !
gh label list --limit 40 2>/dev/null || echo "unavailable" - Open issues: !
gh issue list --state open --limit 20 2>/dev/null || echo "unavailable"
Your task
If the repo line above says NO REMOTE, stop and tell the user this repo has no
GitHub remote yet — the issue workflow needs one. Do not create a repository
yourself; ask them to run gh repo create and say whether it should be public
or private.
-
Check for duplicates in the open issues above. If this overlaps an existing one, say so and ask whether to extend that issue instead of opening a new one.
-
Ground it in the codebase. Read enough to name the packages and files that would actually change. An issue that cannot name its blast radius is not ready to plan against.
-
Write the issue. Keep it short and concrete — this gets read once by a planner:
- Title — imperative, specific (
Add cursor pagination strategy, notPagination improvements). - Context — why this is worth doing, in two or three sentences.
- Acceptance criteria — a checklist of what must be true when it is done. These must be verifiable, not aspirational.
- Affected packages — any combination of
@kavo/core,@kavo/typeorm,@kavo/prisma,@kavo/mongoose,@kavo/nest,@kavo/graphql,@kavo/mcp, and docs. That list is every published package —pnpm-workspace.yamlalso globsexamples/*, which are real workspace packages but private and never released. Cross-check againstPACKAGE_DIRSin.github/workflows/publish.ymlif a new one may have landed. WriteNonefor repo-wiring-only work (.claude/,.github/, tooling) rather than leaving it blank. - Constraints — the invariants that must survive. Check
docs/internals/adr/for ones this issue touches (core purity, registry- driven operations, the explicit barrel, decoration-time routes, soft delete, and relations are common ones) and cite them by number. Also cite the naming conventions inCLAUDE.mdif relevant. Cite only what actually applies; skip the rest. - Out of scope — what this issue deliberately does not cover.
- Title — imperative, specific (
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 · 72 lines · 16 tokens per session scan A a55cbc9ba735
issue is a command published in the GitHub repository kavo-labs/kavo (12 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 933 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
graph-undo
이미 완료(done) 처리된 것을 되돌립니다. 실수로 자동 확정됐을 때 씁니다.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
OPSX: Bulk Archive
Archive multiple completed changes at once.
opsx-bulk-archive
Archive multiple completed changes at once.