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 pod-initgit 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/pod-init)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pod-init"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-init/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/pod-init"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-init.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.00057 | $0.03965 |
| Opus 5.5 | $0.00023 | $0.01586 |
| Sonnet 5.5 | $0.00011 | $0.00793 |
| Haiku 4.5 | $0.00006 | $0.00396 |
Grade A, and why
pod-init scanned grade A with 1 finding 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Prefer `spawnSync('git', ['rev-parse', '--git-dir'])` or the host tool's native argument array. How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to initialize the CocoPlus project bundle in the current working directory.
Pre-flight Check
- Check if
.cocoplus/already exists in the current directory.- If it does: output "CocoPlus is already initialized in this directory. Use
$pod statusto check current state or$pod resumeto restore context." Then stop.
- If it does: output "CocoPlus is already initialized in this directory. Use
- Check that a git repository exists using a shell-safe argument call equivalent to
git rev-parse --git-dir.- Prefer
spawnSync('git', ['rev-parse', '--git-dir'])or the host tool's native argument array. - Do not wrap this in PowerShell-specific parsing or string interpolation.
- If not: offer "Git not detected. Initialize? (yes/no)"
- If yes: run
git initand continue. - If no: stop.
- Prefer
Create Directory Structure
Create the following directories (create them even if empty — they are required by other skills):
.cocoplus/
.cocoplus/lifecycle/
.cocoplus/memory/
.cocoplus/prompts/
.cocoplus/monitors/
.cocoplus/brew/
.cocoplus/grove/
.cocoplus/grove/patterns/
.cocoplus/meter/
.cocoplus/snapshots/
.cocoplus/modes/
.cocoplus/config/
.cocoplus/fleet/
.cocoplus/pull/
.cocoplus/harvest/
.cocoplus/seeds/
.cocoplus/map/
.cocoplus/map/intermediate/
.cocoplus/map/archive/
.cocoplus/flow/
.cocoplus/flow/artifacts/
.cocoplus/flows/
.cocoplus/flows/templates/
.cocoplus/flows/templates/archive/
.cocoplus/proposals/
.cocoplus/proposals/archive/
.cocoplus/routines/
.cocoplus/session/
.cocoplus/personas/
.cocoplus/personas/archive/
.cocoplus/skills/
.cocoplus/cupper/
.cocoplus/recall/
.cocoplus/governance/
.cocoplus/sentinel/
Copy Template Files
Copy template files from the plugin templates directory to .cocoplus/:
-
Copy
templates/AGENTS.md.template→.cocoplus/AGENTS.md- Replace
{{TIMESTAMP}}with current ISO 8601 timestamp - Replace
{{SESSION_ID}}with a generated session ID (format:sess-YYYYMMDD-HHMMSS)
- Replace
-
Copy
templates/project.md.template→.cocoplus/project.md- Replace
{{TIMESTAMP}}with current ISO 8601 timestamp - Prompt the developer: "What is this project called?" Replace
{{PROJECT_NAME}}. - Prompt: "Briefly describe the project (one sentence):" Replace
{{PROJECT_DESCRIPTION}}. - Prompt: "What is the primary goal?" Replace
{{PROJECT_GOAL}}. - Replace
{{OWNER}}with git user name (git config user.name).
- Replace
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.
- 1mo ago First seen · 479 lines · 57 tokens per session scan A 945679cba586
pod-init is a skill published in the GitHub repository Snowflake-Labs/cocoplus (724 stars, last pushed 16d ago), licensed MIT. It adds 57 tokens to every session and 3,965 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
jira-execute
Implement a Jira issue, open a pull request, and report the work on the issue. Insert into the prompt of a Jira column rule that does the building.
jira-merge
Land the pull requests a set of Jira issues carry, in order, resolving a conflict when one appears, and move each card on. Insert into the prompt of a run started on a batch of issues, or of a Jira column rule that ships.
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.