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 pod-statusgit 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/pod-status)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pod-status"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-status/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/pod-status"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-status.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.00055 | $0.01438 |
| Opus 5 | $0.00028 | $0.00719 |
| Sonnet 5 | $0.00011 | $0.00288 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
pod-status 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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to produce a comprehensive status report of the CocoPlus project bundle.
Before proceeding, verify that .cocoplus/ exists in the current directory.
If it does not, output: "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Read State From These Files
Read each file listed below. If a file is missing, use the default value shown. Do NOT error on missing files.
| File | Default if Missing |
|---|---|
.cocoplus/lifecycle/meta.json |
{"current_phase":"not_started","phases_completed":[]} |
.cocoplus/flow.json |
{"stages":[]} |
.cocoplus/memory/decisions.md |
empty |
.cocoplus/meter/current-session.json |
not tracking |
.cocoplus/grove/cupper-findings.md |
no findings |
.cocoplus/modes/ directory listing |
no modes active |
.cocoplus/maturity.json |
not yet computed — run $behavior maturity |
Generate Status Report
Output a structured report with these sections:
1. CocoBrew Lifecycle
- Current phase (from
lifecycle/meta.json) - Phases completed and their timestamps
- Next recommended action
2. CocoFlow Pipeline
- Pipeline name and version (from
flow.json) - Total stages / completed stages / pending stages
- Most recently completed stage
3. Active Modes
Check for presence of these flag files and report on/off:
.cocoplus/modes/memory.on→ Memory Engine.cocoplus/modes/inspector.on→ Environment Inspector.cocoplus/modes/context-mode.on→ Context Mode.cocoplus/modes/quality.on→ Code Quality Advisor.cocoplus/modes/cocometer.on→ CocoMeter.cocoplus/modes/safety.strictorsafety.normalorsafety.off→ Safety Gate level.cocoplus/modes/full-assist.on→ Full Assist Mode
4. Memory Engine
- Mode: on/off
- Decision count (count lines starting with "##" in
memory/decisions.md) - Pattern count (count lines starting with "##" in
memory/patterns.md)
5. CocoMeter
- Current session tokens (from
meter/current-session.jsonif exists) - Sessions tracked (count lines in
meter/history.jsonl)
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.
- 8d ago First seen · 120 lines · 55 tokens per session scan A fd34789711eb
pod-status is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 55 tokens to every session and 1,438 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.