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/luisabwk/kraken/commitgit clone --depth 1 https://github.com/luisabwk/krakenWhat 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.00006 | $0.00187 |
| Opus 5 | $0.00003 | $0.00093 |
| Sonnet 5 | $0.00001 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
commit 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 37 lines · 6 tokens per session scan A 4b8a9c1ee808
commit is a command published in the GitHub repository luisabwk/kraken (1 stars, last pushed 5mo ago), with no licence file. It adds 6 tokens to every session and 187 once invoked, about $0.0000 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 commands, from other repositories
commit-msg
Cursor tooling: skills, rules, subagents.
burndown-full
Drive a partially-executed plan to 100% coverage across the whole repo — enumerate, batch-execute, prove completeness.
plan
Research, clarify requirements, and produce an approved implementation plan before writing code (Cursor Plan Mode).
green-repo
Drive the whole repository to a verified-green baseline — typecheck, lint, tests, build — with authorized fixing of pre-existing debt.
ship-and-observe
Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.
mcp-guide
Reference for the MCP toolset (Context7, Firecrawl, Playwright, Supabase, Sequential Thinking) and when to reach for each.