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.
git 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.callers)<a href="https://agentmods.dev/commands/4tyone/snek/snek.callers"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.callers.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.1 | $0.00005 | $0.00138 |
| Opus 5 | $0.00003 | $0.00069 |
| Sonnet 5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
snek.callers 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 7d 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
Find Callers
Find all places where a function is called in the codebase.
Usage
User provides:
- Function name
- Optional: file pattern to limit search
Steps
- Search for function calls:
# Search for function call patterns
grep -rn "FUNCTION_NAME(" --include="*.EXTENSION" .
-
Filter out the function definition itself.
-
Display results with:
- Caller file and line
- Context showing the call
-
Summarize how many places call this function.
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.
- 7d ago First seen · 32 lines · 5 tokens per session scan A 9f9dc6d95f29
snek.callers 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 138 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
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
doctor
Run read-only health checks on the Kobiton automate plugin (CLI, credentials, profile).
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
trace
Export a Grok session trace locally, or upload it to xAI.
Diagnose
Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…