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 seed-addgit 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/seed-add)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/seed-add"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/seed-add/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/seed-add"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/seed-add.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.00025 | $0.00778 |
| Opus 5 | $0.00013 | $0.00389 |
| Sonnet 5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
seed-add 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$seed add "<idea>" --trigger "<condition>"
Store a deferred idea with an explicit trigger condition. The idea is surfaced by $seed list and the SessionStart hook when the trigger condition is met.
Preconditions
.cocoplus/must be initialized- Both the idea text and a
--triggercondition are required
Arguments
"<idea>"(required): The idea text. Quoted string. Should describe a specific future improvement, feature, or experiment.--trigger "<condition>"(required): A plain-language condition describing when this idea should be acted on. Examples:"when CocoMap is committed"(filesystem check:.cocoplus/map/coco-map.jsonexists)"when Build phase completes"(lifecycle phase check)"when evaluation accuracy exceeds 90%"(manual — always shown as pending manual confirmation)"when CocoMap is active"(mode flag check)
Step-by-Step Behavior
-
Verify initialization: Check
.cocoplus/exists. If not, output: "CocoPlus not initialized. Run$pod initfirst." and exit. -
Validate arguments:
- If idea text is missing, output: "Idea text is required. Use:
$seed add \"<idea>\" --trigger \"<condition>\"" and exit. - If
--triggeris missing, output: "A trigger condition is required. Use:$seed add \"<idea>\" --trigger \"<condition>\"" and exit.
- If idea text is missing, output: "Idea text is required. Use:
-
Generate seed ID: Create a timestamp-based ID:
seed-[YYYYMMDD-HHmmss](compact ISO8601). -
Read current lifecycle phase: Read
.cocoplus/lifecycle/meta.jsonto get the current phase. Use "unknown" if meta.json does not exist. -
Create seeds directory: Ensure
.cocoplus/seeds/exists. Create if missing. -
Write seed file to
.cocoplus/seeds/[seed-id].yaml:id: seed-[timestamp] idea: "[idea text]" trigger: "[trigger condition text]" captured_phase: [current CocoBrew phase] captured_date: [ISO8601] status: pending -
Confirm to developer:
✓ Seed stored as [seed-id] Idea: [idea text] Will surface when: [trigger condition] Run $seed list to check trigger status.
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 · 82 lines · 25 tokens per session scan A be01492a0378
seed-add is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 778 once invoked, about $0.0001 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.
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.
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.
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.
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…
factory-complete-issue
Mark a GitHub issue as done and update its status labels.