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.clonegit 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.clone)<a href="https://agentmods.dev/commands/4tyone/snek/snek.session.clone"><img src="https://agentmods.dev/badge/commands/4tyone/snek/snek.session.clone.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.00004 | $0.00122 |
| Opus 5 | $0.00002 | $0.00061 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
snek.session.clone 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 3d 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
Clone Session
Create a copy of an existing session with all its context and code snippets.
Usage
User should provide:
- Source session ID prefix
- New session name (optional)
Steps
- If no source session provided, list available sessions:
.snek/scripts/list-sessions.sh
- Clone the session:
.snek/scripts/clone-session.sh "SOURCE_SESSION_PREFIX" "NEW_NAME"
- Report the new session ID and confirm it was created.
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.
- 3d ago First seen · 31 lines · 4 tokens per session scan A 2a4b462eede1
snek.session.clone is a command published in the GitHub repository 4tyone/snek (10 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 4 tokens to every session and 122 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
notebook
Low-ceremony capture for ideas (half-formed, want to mature into stories), todos (concrete actions), and notes (durable project/team facts for future recall). One-line capture, conditional elaboration AUQ. Use BEFORE thoughts get forced into stories.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
pipeline
Manage multiple named execution pipelines in one project. Where /mb config manages a single /pipeline.yaml, /mb pipeline lets a project keep several pipelines side by side — each with its own model routing and workflow — and select between them per run or automatically per code-agent host.
search
Search saved conversations by keyword or date.
implement-tdd
Execute TDD workflow following Red → Green → Refactor cycle with .ai-rules standards.