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-demogit 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-demo)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/ops-demo"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/ops-demo/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/ops-demo"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/ops-demo.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.00046 | $0.01557 |
| Opus 5.5 | $0.00018 | $0.00623 |
| Sonnet 5.5 | $0.00009 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
ops-demo 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 1mo 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Activate CocoOps demo mode with a realistic mock dataset so evaluators can explore DORA metrics and sprint health without production Snowflake access.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.
Step 1 — Check Current Demo Status
Read cocoplus.toml and check [demo] enabled. If already true, output:
CocoOps demo mode is already active.
Run $ops dora to view the demo DORA report.
Run $ops demo --reset to regenerate the demo dataset.
Run $ops demo --off to deactivate demo mode.
Then stop (unless --reset flag provided).
Step 2 — Create Demo Dataset Directory
Ensure .cocoplus/ops/demo/ exists. Create it if absent.
Step 3 — Write Demo Metrics Dataset
Write .cocoplus/ops/demo/metrics.json with a realistic 30-day dataset showing DORA metric progression. The dataset must:
- Include representative pipeline names (not generic "pipeline_1" — use realistic names like
stg_orders_load,int_customer_metrics,mart_revenue_daily,ml_churn_predict) - Show a credible improvement arc: early period has higher failure rate and recovery times; later period shows improvement
- Cover all four DORA metrics with plausible values for a data engineering team at High tier (not Elite — believable, not perfect)
{
"dataset_version": "1.0",
"period_days": 30,
"generated_at": "<ISO timestamp>",
"metrics": {
"run_frequency": {
"value": 1.4,
"unit": "per_day",
"tier": "High",
"source": "demo"
},
"lead_time": {
"value": 18.5,
"unit": "hours",
"tier": "High",
"source": "demo"
},
"recovery_time": {
"value": 210,
"unit": "minutes",
"tier": "High",
"source": "demo"
},
"quality_failure_rate": {
"value": 7.2,
"unit": "percent",
"tier": "High",
"source": "demo"
}
},
"pipeline_signals": [
{
"name": "stg_orders_load",
"runs": 38,
"failures": 3,
"avg_lead_time_hours": 14.2,
"last_failure": "2024-01-18T03:22:00Z",
"recovery_minutes": 85
},
{
"name": "int_customer_metrics",
"runs": 30,
"failures": 4,
"avg_lead_time_hours": 22.1,
"last_failure": "2024-01-21T07:45:00Z",
"recovery_minutes": 310
},
{
"name": "mart_revenue_daily",
"runs": 28,
"failures": 1,
"avg_lead_time_hours": 19.8,
"last_failure": "2024-01-09T23:11:00Z",
"recovery_minutes": 42
},
{
"name": "ml_churn_predict",
"runs": 14,
"failures": 4,
"avg_lead_time_hours": 31.4,
"last_failure": "2024-01-23T11:30:00Z",
"recovery_minutes": 480
}
],
"git_signals": {
"commits_14d": 18,
"pipeline_prs": 6
},
"sprint": {
"start": "2024-01-15",
"end": "2024-01-29",
"velocity_units": 9,
"daily_burn_rate": 0.9,
"predicted_final_velocity": 12.6
},
"overall_health": "High"
}
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.
- 1mo ago First seen · 194 lines · 46 tokens per session scan A 8fdb27b36af8
ops-demo is a skill published in the GitHub repository Snowflake-Labs/cocoplus (727 stars, last pushed 24d ago), licensed MIT. It adds 46 tokens to every session and 1,557 once invoked, about $0.0002 per session on Opus 5.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
iterate-prd
Only use when the user explicitly invokes this skill by name.
iterate-structure-outline
Only use when the user explicitly invokes this skill by name.
feature-requirements
Turn the ticket into requirements and CUJs, and stop with a split proposal when it is too big.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
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…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.