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.blame)<a href="https://agentmods.dev/commands/4tyone/snek/snek.blame"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.blame.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.00009 | $0.00124 |
| Opus 5 | $0.00005 | $0.00062 |
| Sonnet 5 | $0.00002 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
snek.blame 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 8d 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
Git Blame
Show who last modified each line of a file.
Usage
User provides:
- File path
- Optional: line range (e.g., "10-25")
Steps
- Run git blame:
# Entire file
git blame "/path/to/file"
# Specific lines
git blame -L START,END "/path/to/file"
- Display results showing:
- Commit hash
- Author
- Date
- Line content
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.
- 8d ago First seen · 33 lines · 9 tokens per session scan A 34d041e2499e
snek.blame is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 124 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
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
Review staged changes and create a commit.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
allow-skip-hooks
Arm the hook-skip-blocker to permit the next N git commands with --no-verify / --no-gpg-sign / -c commit.gpgsign=false / -c core.hooksPath=. Default N = 1.
update-changelog
Append a dated line to the project's canonical CHANGELOG.md (the "what shipped, newest first" record) via propose-confirm — one writer, several callers.
pre-push
Run the pre-push pre-flight checklist before pushing — commits-to-ship summary, branch-name / commit-hygiene / AI-attribution / debug-artifact / hook-bypass checks; stops on any flag.