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 recipe-usegit 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/recipe-use)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/recipe-use"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/recipe-use/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/recipe-use"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/recipe-use.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.00815 |
| Opus 5 | $0.00023 | $0.00407 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
recipe-use 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to generate a CocoFlow pipeline from a named recipe template.
Pre-flight Check
Check that .cocoplus/ exists. If not:
Output: "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Locate Recipe Template
Look for <name>.json.template in:
~/.coco/plugins/cocoplus/recipes/<name>.json.template.cocoplus/recipes/<name>.json.template(project-local)
If not found in either location, output:
"Recipe '' not found. Run $recipe list to see available recipes." Then stop.
Read Parameters
Read the __recipe_meta block from the template to identify required parameters, optional parameters, and their descriptions.
Collect Parameter Values
For each required parameter not already supplied via --params key=value:
- Ask the developer interactively with a clear prompt showing the parameter name and description
- Wait for response before proceeding to the next missing parameter
Validate all collected values:
- Non-empty for required parameters
- Snowflake identifier format where specified (alphanumeric + underscores, no spaces)
If any validation fails, explain the format requirement and re-prompt (do not abort).
Check for Existing flow.json
If .cocoplus/flow.json already exists:
Output: "A flow.json already exists for this project. Overwrite it with the recipe pipeline? (y/n)"
Wait for confirmation. If declined, stop.
Generate Pipeline
Replace all {{parameter_name}} slots in the template with supplied values.
Remove the __recipe_meta block from the output.
Validate the resulting JSON against the CocoFlow schema (check that nodes array exists and each node has id, label, type, agent fields). If validation fails, output the specific schema violations and do not write.
Write to flow.json
Write the validated JSON to .cocoplus/flow.json.
Output
Generated: <name> pipeline (<N> stages)
Parameters used:
<param1> = <value1>
<param2> = <value2>
Pipeline stages:
1. <stage-id> (<agent>, <model>)
2. <stage-id> (<agent>, <model>) [plan gate]
...
Written to .cocoplus/flow.json
Next: Run $plan to review and approve before executing.
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 · 98 lines · 46 tokens per session scan A 4ae2ab290135
recipe-use is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 815 once invoked, about $0.0002 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
prompt-engineering
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, designing production prompt templates, or building AI-powered features.
cron
Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool. Use when asked to remind, schedule a recurring or one-shot task, try a job now, or manage jobs that fire unattended.
cncf-landscape
Use this skill when discovering and comparing cloud-native technologies from the CNCF Landscape for an architecture or engineering decision. Query the live public Landscape API, filter candidates by capability, category, maturity, license, and repository signals, then produce an evidence-backed shortlist with…
terraform
Operate Terraform and OpenTofu across the whole infrastructure lifecycle: module structure, state backends and locking, plan/apply workflow, drift detection, remote state, upgrade and refactor flows, and evidence-based diagnostics. Use when running or inspecting terraform plans, applies, state files, imports, or state…
go-to-market
Plan and evaluate go-to-market strategy using positioning, acquisition, growth economics, market-entry, and competitive-response workflows. Do not use for CRM execution, product strategy, legal interpretation, or visual brand design. (April Dunford's positioning, message hierarchy), customer acquisition strategy…
zcfg
Integrate zcfg (Zero Dependency Configuration Utility) into Java applications. Use when adding configuration loading, reading properties files, setting up application configuration, or integrating zcfg into a Java project. Triggers on "zcfg", "add configuration", "load properties", "application configuration with…