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/4tyone/snek/snek.complexitygit clone --depth 1 https://github.com/4tyone/snekWhat 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.00003 | $0.00158 |
| Opus 5 | $0.00002 | $0.00079 |
| Sonnet 5 | $0.00001 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
snek.complexity 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
Analyze Complexity
Analyze the complexity of a function or file.
Usage
User provides:
- File path
- Optional: specific function name
Steps
- Get file outline:
.snek/scripts/get-file-outline.sh "/path/to/file"
-
Read and analyze the code for:
- Cyclomatic complexity (branches, loops)
- Nesting depth
- Function length
- Number of parameters
- Dependencies
-
Report findings:
- Complexity score/rating
- Specific concerns (deeply nested, too many params, etc.)
- Suggestions for simplification
-
If issues found, suggest refactoring approaches.
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 · 37 lines · 3 tokens per session scan A 57855dbef097
snek.complexity is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 158 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
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
security
The security pass: secrets (blocking), SAST, dependency vulns — plus the index's entry points to review from.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
setup
Fetch Kobiton credentials from the authenticated MCP server and write them to /.kobiton/.credentials.