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 cocoharvestgit 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/cocoharvest)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/cocoharvest"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/cocoharvest/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/cocoharvest"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/cocoharvest.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.00068 | $0.02788 |
| Opus 5 | $0.00034 | $0.01394 |
| Sonnet 5 | $0.00014 | $0.00558 |
| Haiku 4.5 | $0.00007 | $0.00279 |
Grade A, and why
cocoharvest 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to decompose the approved plan into parallel workstreams and generate a complete flow.json pipeline.
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 .cocoplus/lifecycle/plan.md. If it does not exist or is empty:
Output: "No approved plan found. Run $plan to create an execution plan first." Then stop.
Step 1: Parse Workstreams
Read .cocoplus/lifecycle/plan.md section ## Workstreams.
Extract each workstream as a discrete unit of work with:
- Name
- Description
- Dependencies (other workstreams this depends on)
- Artifacts it produces
Step 2: CocoLens — HITL/AFK Stage Classification
For each workstream, classify it as HITL (Human In The Loop) or AFK (Away From Keyboard) before assigning a persona:
- HITL: The stage requires human judgment before it can proceed or before its output is consumed. Classify as HITL when: the stage makes architectural decisions, involves evaluation methodology choices, writes to production schemas, deploys or alters Snowflake objects with EHRB indicators, or its output is ambiguous enough that autonomous resolution could be incorrect.
- AFK: The stage can run and complete autonomously without developer input. Classify as AFK when: the stage implements a well-specified deliverable, the success criteria are unambiguous, and the stage's on_failure behavior is clear.
Write hitl: true or hitl: false to each stage's flow.json definition. HITL stages suspend pipeline execution after completion and surface a developer review prompt before downstream stages are spawned. The developer may override the classification: output the HITL/AFK assignment for each stage and ask "Does this classification look right? (yes / override <hitl|afk>)" before writing flow.json.
Step 3: Classify Workstreams by Domain
For each workstream, classify its primary domain using this mapping:
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 · 241 lines · 68 tokens per session scan A fa5e41cf130f
cocoharvest is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 2,788 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.
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.
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…
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.