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-listgit 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-list)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/seed-list"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/seed-list/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-list"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/seed-list.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.00026 | $0.00855 |
| Opus 5 | $0.00013 | $0.00428 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
seed-list 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$seed list
Evaluate all stored seeds against current project state. Shows two sections: seeds Ready to Promote (trigger has fired) and seeds Waiting (trigger not yet met).
Preconditions
.cocoplus/must be initialized.cocoplus/seeds/directory may be empty (outputs "No pending seeds" if so)
Step-by-Step Behavior
-
Verify initialization: Check
.cocoplus/exists. If not, output: "CocoPlus not initialized. Run$pod initfirst." and exit. -
Read all seed files: Load all
.yamlfiles from.cocoplus/seeds/withstatus: pendingorstatus: triggered. Skip seeds withstatus: promotedorstatus: discarded. -
If no seeds found: Output: "No pending seeds. Add ideas with
$seed add." and exit. -
Evaluate each trigger condition against current project state:
Filesystem presence checks:
- "when coco-map.json exists" / "when CocoMap is committed" → check
.cocoplus/map/coco-map.json - "when [feature] is active" → check corresponding mode flag in
.cocoplus/modes/ - "when [filename] exists" → check for that file in
.cocoplus/
Lifecycle phase checks:
- "when Build phase completes" → read
.cocoplus/lifecycle/meta.json, check ifbuildphase is in completed phases - "when Ship phase completes" → check if lifecycle phase is "shipped"
- "when [phase] phase begins" → check current phase field
Mode flag checks:
- "when [feature] is enabled" → check
.cocoplus/modes/[feature].on
Manual conditions (plain language not matching above patterns):
- Always show as "pending manual confirmation" — do not auto-trigger
- "when coco-map.json exists" / "when CocoMap is committed" → check
-
Update triggered status: For any seed whose condition just fired (was
pending, now evaluates as triggered), update its.yamlfile: setstatus: triggered, addtriggered_date: [ISO8601]. -
Display output in two sections:
Seeds Ready to Promote ([N]):
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[seed-id] — [idea]
Triggered: [trigger condition that fired]
Captured during: [captured_phase] phase on [captured_date]
Promote with: $seed promote [seed-id]
[repeat for each triggered seed]
Seeds Waiting ([N]):
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[seed-id] — [idea]
Waiting for: [trigger condition]
Status: [not yet / pending manual confirmation]
Captured during: [captured_phase] phase on [captured_date]
[repeat for each waiting seed]
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 · 92 lines · 26 tokens per session scan A ee01607a9b31
seed-list is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 855 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.
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.