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 ops-doragit 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/ops-dora)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/ops-dora"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/ops-dora.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.1 | $0.00052 | $0.01317 |
| Opus 5 | $0.00026 | $0.00659 |
| Sonnet 5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
ops-dora 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Compute the four DORA-adapted CocoOps metrics and produce a delivery intelligence report.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.
Step 1 — Check Demo Mode
Read cocoplus.toml if it exists and check [demo] enabled. If demo mode is active, read data from .cocoplus/ops/demo/ instead of production sources.
Step 2 — Run Deterministic Metrics Computation
Compute the metrics directly with Coco-native tools:
- If demo mode is active, read
.cocoplus/ops/demo/and use its task-history and incident fixtures. - Otherwise query Snowflake task history with
SnowflakeSqlExecuteand collect deployment/change evidence fromgit log. - Compute the four DORA-adapted indicators deterministically from the collected rows:
- Pipeline Run Frequency: successful production pipeline runs per day.
- Data Availability Lead: median time from committed change to successful scheduled availability.
- Failure Recovery Time: median time from failing task/incidence record to the next successful run.
- Data Quality Failure Rate: failed or rolled-back data quality runs divided by total runs.
- Write
.cocoplus/ops/dora-snapshot.jsonatomically with the raw counts, computed values, benchmark tiers, source mode, andcomputed_at.
If Snowflake is unavailable and no demo data exists, output: "CocoOps: unable to compute metrics — [reason]. Run $ops demo to activate demo mode for evaluation." Then stop.
Step 3 — Read Snapshot
Read .cocoplus/ops/dora-snapshot.json for the computed metrics.
Verify the snapshot includes benchmarks with the DORA-adapted tier thresholds used to classify each metric. If absent, add the threshold context to the report narrative from the skill definition before displaying tiers, so "Elite/High/Medium/Low" is never presented without benchmark meaning.
Step 4 — Spawn Haiku Narrative Synthesis
Pass the pre-computed metrics snapshot to a Haiku sub-agent with this mandate:
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 · 108 lines · 52 tokens per session scan A 705d1f3ad4b9
ops-dora is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 1,317 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
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…
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.
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.
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.
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.
factory-complete-issue
Mark a GitHub issue as done and update its status labels.