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 fleet-stopgit 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/fleet-stop)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/fleet-stop"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/fleet-stop/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/fleet-stop"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/fleet-stop.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.00040 | $0.00687 |
| Opus 5 | $0.00020 | $0.00344 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
fleet-stop 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to stop a running CocoFleet.
Before proceeding, verify that .cocoplus/ exists.
If not: output "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Parse argument: $fleet stop [fleet-id]
If no fleet-id: output "Usage: $fleet stop [fleet-id]" Then stop.
Read .cocoplus/fleet/[fleet-id]-state.json. If not found: output "Fleet state not found for [fleet-id]." Then stop.
Terminate Running Instances
For each instance with status == "running":
- Read PID from state.json
- Terminate the process using cross-platform Node.js via the Bash tool:
node -e "try{process.kill([pid],'SIGTERM')}catch(e){}" - Wait up to 10 seconds for graceful shutdown, checking liveness each second:
node -e " const pid=[pid]; let waited=0; const iv=setInterval(()=>{ try{process.kill(pid,0);waited++;} catch(e){clearInterval(iv);} if(waited>=10){try{process.kill(pid,'SIGKILL')}catch(_){}clearInterval(iv);} },1000);" - Update state.json: status = "stopped", completed_at = [timestamp]
Write Stop Record
Write .cocoplus/fleet/[fleet-id]-stop-record.md:
# Fleet Stop Record
**Fleet ID:** [fleet-id]
**Stopped At:** [ISO 8601 timestamp]
## Instances Stopped
| Instance | Last Status | Last Checkpoint | PID |
|----------|-------------|-----------------|-----|
[one row per stopped instance]
Output: "Fleet [fleet-id] stopped. [N] processes terminated. Stop record: .cocoplus/fleet/[fleet-id]-stop-record.md."
Anti-Rationalization
| Shortcut / Temptation | Why It Fails |
|---|---|
| Skip SIGKILL after SIGTERM timeout | A process that ignores SIGTERM will keep running and orphan log files; SIGKILL ensures termination |
| Update state.json before sending signals | State must reflect reality — only mark "stopped" after confirming the process is dead |
| Skip writing the stop record | The stop record is audit evidence; missing it means no trace of when/why the fleet was halted |
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 · 72 lines · 40 tokens per session scan A cf6f374b5a05
fleet-stop is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 687 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.
openkb-html-critic
Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every…
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.
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…