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.explaingit clone --depth 1 https://github.com/4tyone/snekWrote 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/4tyone/snek/snek.explain)<a href="https://agentmods.dev/commands/4tyone/snek/snek.explain"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.explain.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.00006 | $0.00178 |
| Opus 5 | $0.00003 | $0.00089 |
| Sonnet 5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
snek.explain 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 4d 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
Explain Code
Explain what a piece of code does.
Usage
User provides:
- File path
- Line number or line range (e.g., "10-25")
- Or: function/struct name to find and explain
Steps
-
If line range provided, read that section:
- Read the file
- Extract the specified lines
-
If function/struct name provided:
- Use outline script to find it:
.snek/scripts/get-file-outline.sh "/path/to/file"- Read the relevant section
-
Analyze and explain:
- What the code does
- Key logic and data flow
- Important patterns or techniques used
- Any potential issues or considerations
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.
- 4d ago First seen · 35 lines · 6 tokens per session scan A 53e1d074240c
snek.explain is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 178 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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
setup
Fetch Kobiton credentials from the authenticated MCP server and write them to /.kobiton/.credentials.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.