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 cocoopsgit 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/cocoops)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/cocoops"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/cocoops/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/cocoops"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/cocoops.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.00053 | $0.00679 |
| Opus 5 | $0.00026 | $0.00340 |
| Sonnet 5 | $0.00011 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
cocoops 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
You are the CocoOps dispatch router. Route $ops sub-commands to the appropriate CocoOps sub-skills.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.
Routing Table
| Command | Sub-skill | Description |
|---|---|---|
$ops dora |
ops-dora.skill.md |
DORA-adapted delivery metrics |
$ops sprint |
ops-sprint.skill.md |
Current sprint health |
$ops suggest |
ops-suggest.skill.md |
Time-aware operational suggestions |
$ops demo |
ops-demo.skill.md |
Activate demo mode |
$ops refresh |
ops-dora.skill.md |
Re-run DORA computation and update snapshot |
$ops (no args) |
Show dashboard summary | Display last dora-snapshot.json summary with color-coded metric cards in text form |
$ops dashboard |
Show dashboard summary | Alias for $ops default dashboard |
Default View (no args)
If invoked with no sub-command, display a brief status dashboard:
CocoOps — <project> — <date>
Last DORA snapshot: <timestamp or "None — run $ops dora">
Overall health: <tier or "Unknown">
Metric cards:
Pipeline Run Frequency [GREEN/YELLOW/RED] <value> <tier>
Data Availability Lead [GREEN/YELLOW/RED] <value> <tier>
Failure Recovery Time [GREEN/YELLOW/RED] <value> <tier>
Quality Failure Rate [GREEN/YELLOW/RED] <value> <tier>
Trend bands:
Use dora-thesis.md when present to summarize improving / flat / worsening longitudinal direction.
Quick commands:
$ops dora — Compute full DORA metrics
$ops sprint — Current sprint health
$ops suggest — What to focus on now
$ops demo — Activate demo mode
Read .cocoplus/ops/dora-snapshot.json for the summary data. If absent, suggest running $ops dora.
Exit Criteria
- All sub-commands route to correct sub-skills
- Default view shows last snapshot summary
- Unknown sub-commands show routing table with available options
Anti-Rationalization
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 · 72 lines · 53 tokens per session scan A 25e3b5053ddc
cocoops is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 679 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.