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 trace-blastgit 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/trace-blast)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/trace-blast"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/trace-blast/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/trace-blast"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/trace-blast.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.00031 | $0.00308 |
| Opus 5 | $0.00015 | $0.00154 |
| Sonnet 5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
trace-blast 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 5d 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.
This is a copy
97% identical to audit-ci — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Your objective is to perform this V2-native feature behavior using Coco-native capabilities: Read, Write, Edit, Bash when explicitly needed by the host, Snowflake tools when the feature requires data access, and subagents when the feature requires independent review.
Required Contract
- Preserve the artifact paths, schemas, and user-visible outputs documented by the owning feature skill.
- Do not call legacy scripts as the implementation path.
- Prefer deterministic file parsing and structured artifacts over free-form prose when producing machine-readable state.
- If an external side effect would occur, apply the same gate and confirmation semantics as the owning feature.
Exit Criteria
- The owning feature's documented artifact is produced or updated.
- The output schema remains compatible with existing readers.
- No registered runtime script invocation is required.
Anti-Rationalization
| Shortcut / Temptation | Why It Fails |
|---|---|
| Treat the skill as complete because the file exists | Skill contracts must describe observable behavior and verification, not just command names. |
| Skip artifact and safety checks for a small command | Small commands still mutate state or guide execution; preserve the same gates. |
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.
- 5d ago First seen · 32 lines · 31 tokens per session scan A b2cc587483d2
trace-blast is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 308 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to audit-ci, differing in 4 lines, and is treated as a copy.
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.
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…