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.session.infogit 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.session.info)<a href="https://agentmods.dev/commands/4tyone/snek/snek.session.info"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.session.info.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.00006 | $0.00095 |
| Opus 5 | $0.00003 | $0.00048 |
| Sonnet 5 | $0.00001 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
snek.session.info 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 6d 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
Session Info
Show detailed information about the currently active snek session.
Steps
- Get active session info:
.snek/scripts/get-active-session.sh
- Display:
- Session ID
- Session name
- Max tokens setting
- List of context files
- Number of code snippets
- Last updated time
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.
- 6d ago First seen · 25 lines · 6 tokens per session scan A 757d78eb9892
snek.session.info 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 95 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
catchup
Rebuild context after /clear or starting a new session.
plan
Create a detailed work plan with DoD and save it in memory-bank.
start
Load current project context from memory-bank.
Update
Update the Evyasys plugin and manage context compression — shows version diff, changelog highlights, asks for confirmation, then always asks about compression state. Project config, credentials, docs, and board artefacts are never touched.
memory-review
Run the memory review — staleness, duplicates, graduation candidates.
catchup
Reload the current context after a reset or compaction.