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 buildgit 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/build)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/build"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/build/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/build"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/build.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.00967 |
| Opus 5 | $0.00026 | $0.00483 |
| Sonnet 5 | $0.00011 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
build 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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing the Build phase (3/6) of CocoBrew. Your objective is to transform the approved plan into executing workstreams.
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/meta.json. Verify phases_completed contains both "spec" and "plan".
If not: output "The Spec and Plan phases must be completed before building. Check $pod status for current state." Then stop.
Verify that the artifact files actually exist on disk — meta.json alone is not sufficient:
- Check
.cocoplus/lifecycle/spec.mdexists. If not: output "spec.md is missing from.cocoplus/lifecycle/. The Spec phase record is incomplete. Re-run$specto regenerate it." Then stop. - Check
.cocoplus/lifecycle/plan.mdexists. If not: output "plan.md is missing from.cocoplus/lifecycle/. The Plan phase record is incomplete. Re-run$planto regenerate it." Then stop.
SecondEye Gate Check
Scan .cocoplus/lifecycle/ for any files matching secondeye-*.md.
For each file found, check YAML frontmatter for critical_open: true and acknowledged: false.
If any such file exists:
- Output: "Unacknowledged critical findings from SecondEye review. Run
$secondeye acknowledgeto review and acknowledge before building." - List the finding summaries.
- Stop.
Complexity Assessment
Read .cocoplus/lifecycle/plan.md. Assess complexity:
- Count workstreams listed in the plan
- Identify if multiple personas are required
- Check if any stages have external dependencies
If 3 or more workstreams OR multiple personas required: → Complexity = HIGH → invoke CocoHarvest automatically
If fewer than 3 workstreams AND single persona sufficient: → Complexity = LOW → offer simple execution without CocoHarvest
Tell the developer the complexity assessment and proceed accordingly.
Invoke CocoHarvest (for HIGH complexity)
Activate the cocoharvest skill to:
- Decompose plan.md into parallel workstreams
- Assign personas
- Generate flow.json stages
- Create per-stage prompt files in
.cocoplus/prompts/
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.
- 6d ago First seen · 93 lines · 53 tokens per session scan A 26aaf1eb63bc
build is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 967 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.
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-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.