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.doc.functiongit 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.00005 | $0.00195 |
| Opus 5 | $0.00003 | $0.00097 |
| Sonnet 5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
snek.doc.function 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.
What it actually says
Document Function
Generate documentation for a specific function.
Usage
User provides:
- File path
- Function name or line number
Steps
- Get file outline to locate function:
.snek/scripts/get-file-outline.sh "/path/to/file"
-
Read the function code.
-
Generate documentation including:
- Brief description of what the function does
- Parameters with types and descriptions
- Return value description
- Example usage (if applicable)
- Any important notes or caveats
-
Format documentation in the appropriate style for the language:
- Rust:
///doc comments - Python: docstring with Google/NumPy style
- JavaScript/TypeScript: JSDoc
- Go: godoc style
- Rust:
-
Present the documentation for user to apply.
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 · 40 lines · 5 tokens per session scan A 22ed949f7303
snek.doc.function is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 195 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
idea
想法到产品端到端教练 — 一句话想法走到 PRD + 可点击 HTML 原型（会顶嘴、强制砍功能）.
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.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
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.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.