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 skills/verivus-oss/llm-cli-gateway/session-workflownpx skills add verivus-oss/llm-cli-gateway --skill session-workflowgit clone --depth 1 https://github.com/verivus-oss/llm-cli-gatewayWrote 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/skills/verivus-oss/llm-cli-gateway/session-workflow)<a href="https://agentmods.dev/skills/verivus-oss/llm-cli-gateway/session-workflow"><img src="https://agentmods.dev/badge/skills/verivus-oss/llm-cli-gateway/session-workflow.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.00046 | $0.02559 |
| Opus 5 | $0.00023 | $0.01280 |
| Sonnet 5 | $0.00009 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
session-workflow 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Workflow
Separate gateway bookkeeping from native provider continuity. session_create,
session_list, session_set_active, and session_get manage gateway metadata;
they do not create or prove a provider-native conversation. Never pass a
gateway-generated ID to a provider as though it were a native handle.
For a review session, dispatch requests through the local stdio gateway MCP surface. A session does not authorize a direct provider CLI, connector/shadow gateway, or shell fallback.
Discover before resuming
Before using a provider-specific session field, query:
provider_tool_capabilities({cli:"claude"})
provider_tool_capabilities({cli:"codex"})
provider_tool_capabilities({cli:"gemini"})
provider_tool_capabilities({cli:"grok"})
provider_tool_capabilities({cli:"mistral"})
provider_tool_capabilities({cli:"devin"})
provider_tool_capabilities({cli:"cursor"})
Use a native sessionId only when it came from that provider or was supplied by
the caller as a verified native handle. A fresh gateway session often uses a
gw-* bookkeeping ID. It is not resumable for Codex, Grok, Mistral, Devin, or
Cursor, and must never be replayed to Gemini either.
Native continuity matrix
| Provider | Native resume | Important boundary |
|---|---|---|
| Claude | sessionId maps to --session-id; continuation maps to --continue. |
Managed native continuation is a high-risk posture input requiring an approval decision and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1. |
| Codex | Real Codex UUID maps to codex exec resume <UUID>; resumeLatest:true resumes a previous session through --last. |
Do not rely on the resumed cwd or on which session --last selects (#258). Use a real UUID for a specific Codex session. Resume drops sandboxMode and fullAuto, though configOverrides can still set sandbox_mode. |
| Gemini | A caller-owned Antigravity conversation ID maps to --conversation; resumeLatest:true maps to --continue. |
Fresh launches do not produce a reusable native ID. Check resumable:true; never replay gw-*. |
| Grok | Native ID maps to --resume; resumeLatest:true maps to --continue. |
A fresh gw-* ID is bookkeeping only. Cwd affects --continue context. |
| Mistral | Native ID maps to --resume; resumeLatest:true maps to --continue. |
A fresh gw-* ID is bookkeeping only. Vibe session logging defaults on; doctor --json flags only explicit [session_logging] enabled = false. |
| Devin | Native ID maps to --resume; resumeLatest:true maps to --continue. |
A fresh gw-* ID is bookkeeping only. Use workingDir or workspace to bind the selected cwd. |
| Cursor | Native chat/session ID maps to --resume; resumeLatest:true maps to --continue. |
A fresh gw-* ID is bookkeeping only. Use workingDir for its checkout, or a verified workspace. |
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.
- 5d ago First seen · 217 lines · 46 tokens per session scan A 0137300d0fe3
session-workflow is a skill published in the GitHub repository verivus-oss/llm-cli-gateway (15 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 2,559 once invoked, about $0.0002 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-30.
Other skills, from other repositories
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
deep-execution
Executes agent-enhanced council queries by spawning parallel Claude subagents that each query a provider, evaluate response quality, ask follow-up questions, and return structured insights with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex architectural decisions…
bug-audit
Weekly multi-agent audit for serious bugs (data integrity, silent caps, staleness, timestamp math, trust boundaries). Fans out Sonnet scanners + Opus deep auditors, adversarially verifies every finding, files GitHub issues for confirmed critical/high bugs. Trigger: /bug-audit.
provider-integration
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API…
architect
System design, tradeoffs, and complex technical decisions.