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/zach-source/mcp-rust-proxy/mcp-proxy-start-sessiongit clone --depth 1 https://github.com/zach-source/mcp-rust-proxyWhat 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.00009 | $0.00144 |
| Opus 5 | $0.00005 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
mcp-proxy-start-session 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
Start a new tracking session to group all responses in this conversation.
Arguments:
- $1: User's original question/request (optional)
Example: /mcp-proxy:start-session "Help me build a REST API"
Instructions for Claude:
- Call mcp__proxy__tracing__start_session tool with:
- user_query: $1 (if provided)
- Store the returned session_id for reference
- Inform user: "Session tracking started - all responses will be grouped"
- Mention that they can end the session with /mcp-proxy:end-session
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 · 20 lines · 9 tokens per session scan A 0f5d530632f7
mcp-proxy-start-session is a command published in the GitHub repository zach-source/mcp-rust-proxy (5 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 144 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
load
Session lifecycle management with Serena MCP integration for project context loading.
save
Session lifecycle management with Serena MCP integration for session context persistence.
AI: Handoff
Generate a HANDOFF.md snapshot of session state for cross-session continuity.
INFO
Каждый новый терминал = новая сессия = пустой контекст. Агент не знает по какому проекту работаем, какой стек, какие серверы, где деплой, какие активные задачи. Пользователь вынужден на каждом старте перечислять одно и то же — теряется время и мысль.
import-codex
Import Codex session(s) into Claude Code, then resume into them.
load
Session lifecycle management with Serena MCP integration for project context loading.