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 skills add Snowflake-Labs/cocoplus --skill sessiongit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/snowflake-labs/cocoplus/session)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/session"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/session/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/session"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/session.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01174 |
| Opus 5 | $0.00026 | $0.00587 |
| Sonnet 5 | $0.00010 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to manage CocoSession, the continuity and operator-control layer for long-running CocoPlus work.
Commands
$session status: read.cocoplus/session/PROGRESS.md,.cocoplus/session/CONTEXT.md,.cocoplus/session/iteration-budget.json,.cocoplus/session/budget-state.json,.cocoplus/session/status.json,.cocoplus/pod-state.json,.cocoplus/AGENT_STOP, and.cocoplus/STEER.md; report handoff freshness, active predicate state, queued work count, iteration budget, cost-budget state, terminal status, kill-switch state, and pending steering.$session progress: show the four handoff sections from.cocoplus/session/PROGRESS.md: Done, In Progress, Next, Notes.$session steer "<instruction>": write the instruction to.cocoplus/STEER.md. The UserPromptSubmit hook injects it once, appends a session event, then clears the file.$session stop: create.cocoplus/AGENT_STOPwith timestamp, operator, and reason. The PreToolUse hook blocks tool use while the sentinel exists.$session resume: remove.cocoplus/AGENT_STOPafter confirming the operator intends to resume.
Continuity Contract
Every CocoFlow or long-running operator session must be recoverable from files alone:
.cocoplus/session/PROGRESS.mdis the human handoff..cocoplus/session/CONTEXT.mdis machine-greppable predicate state inCLASS.key=valueform..cocoplus/session/task-queue.jsonlrecords mid-session requests without replacing the active item.- New work is queued under Next unless the operator explicitly changes the current item.
.cocoplus/session/iteration-budget.jsontracks cap, consumed turns, warning threshold, and stop state..cocoplus/session/budget-state.jsontracksnormal,reserve, orexhaustedcost-budget state. Budget checks happen at stage boundaries only; in-flight stages are never interrupted..cocoplus/session/status.jsonand.cocoplus/pod-state.jsonuse the canonical status vocabulary:running,paused,completed,exited,failed,idle,retired.
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.
- 9d ago First seen · 90 lines · 52 tokens per session scan A 0a97547d7dd6
session is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 1,174 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
task-dependency-patterns
Task Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status.
herdr-kit-workflows
Set up and operate Herdr Kit safely: install and configure the plugin and Mastra Code integration, manage Review and Work repository scope, open primary repository workspaces, synchronize managers, materialize or dematerialize managed worktrees, and update Herdr Kit settings or shortcuts.
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.
herdr-manager-query
Query the authoritative global Herdr Review and Work Manager inventory, recommend actionable PR work, and explicitly materialize confirmed remote-only Review Manager records through the plugin's stable public CLI.
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
factory-complete-issue
Mark a GitHub issue as done and update its status labels.