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/lakpriya1s/agent-rack/session-startnpx skills add lakpriya1s/agent-rack --skill session-startgit clone --depth 1 https://github.com/lakpriya1s/agent-rackWrote 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/lakpriya1s/agent-rack/session-start)<a href="https://agentmods.dev/skills/lakpriya1s/agent-rack/session-start"><img src="https://agentmods.dev/badge/skills/lakpriya1s/agent-rack/session-start.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.00018 | $0.00434 |
| Opus 5 | $0.00009 | $0.00217 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
session-start 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 4d 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 background sub-agent session through agent-rack's agent_session_create MCP tool.
Raw slash-command arguments:
$ARGUMENTS
Parsing
Same shape as /agent-rack:run: first word is the agent id, the rest (minus flags) is the
prompt. Recognized flags: --workspace <path>, --mode <mode>.
If no agent id is given, call mcp__plugin_agent-rack_agent-rack__agent_list_available and ask rather than
guessing.
When to prefer this over /agent-rack:run
Use this instead of the synchronous /agent-rack:run when the task is long-running, or the
user wants to keep working while it runs in the background, or they'll want to send follow-up
input mid-task.
Execution
Call mcp__plugin_agent-rack_agent-rack__agent_session_create with agent and prompt, plus workspace/mode
if given. It returns immediately with a sessionId and status: "running" — it does not block.
Output
Report the sessionId clearly and tell the user how to follow up:
/agent-rack:session-status <sessionId>for current status/summary/agent-rack:session-logs <sessionId>to tail the raw event stream/agent-rack:session-send <sessionId> <message>to send follow-up input/agent-rack:session-cancel <sessionId>to stop it early
Do not poll status yourself in this command — starting the session is the entire job.
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.
- 4d ago First seen · 42 lines · 18 tokens per session scan A 511b0eeabfbc
session-start is a skill published in the GitHub repository lakpriya1s/agent-rack (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 434 once invoked, about $0.0001 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 skills, from other repositories
cao-workflow
Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…
cao-plugin
Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…
cao-provider
Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…
cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.
agui-author
Author live dashboard UI from an agent via the emitui MCP tool. Emit one of six allow-listed components (approvalcard, choiceprompt, diffsummary, progress, metric, agentcard) with JSON props and it renders in any AG-UI client watching the fleet. Use when you want the operator to see a decision, a diff, or a status…