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 agentmods add skills/snowflake-labs/cocoplus/context-addnpx skills add Snowflake-Labs/cocoplus --skill context-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/context-add)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/context-add"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/context-add.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.01225 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
context-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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your objective is to capture organizational standards into a versioned context file.
Pre-flight Check
Check that .cocoplus/ exists. If not:
Output: "CocoPlus not initialized in this directory. Run $pod init to begin." Then stop.
Present Category Menu
Output:
Which context would you like to add or update?
1. approved-models — Which Cortex models are approved for use
2. quality-thresholds — Minimum accuracy and performance standards
3. pii-policy — PII handling rules for AI functions
4. warehouse-policy — Which warehouses to use for which query types
5. naming-conventions — Object naming standards for Snowflake objects
6. governance-gates — Required approval steps before production deployment
Wait for the developer to select a number (1–6).
Map selection to filename:
- 1 →
approved-models.md - 2 →
quality-thresholds.md - 3 →
pii-policy.md - 4 →
warehouse-policy.md - 5 →
naming-conventions.md - 6 →
governance-gates.md
Check Existing Content
If .cocoplus/context/<category>.md already exists, read and display it, then ask:
"This file already exists. Would you like to update it (add/change entries) or replace it entirely?"
Wait for response before proceeding.
Collect Standards via Dialogue
For the selected category, ask 5–10 targeted questions. Examples per category:
approved-models:
- Which Cortex models are approved for production classification tasks? (e.g., mistral-large2, llama3.1-70b)
- Which models are approved for extraction/NER tasks?
- Are there models that are explicitly blocked? Why?
- Is there a default model to use when none is specified?
- Any cost or latency constraints that restrict model choice?
quality-thresholds:
- What is the minimum classification accuracy required for production? (e.g., 85%)
- Maximum acceptable p95 latency for AI function calls? (e.g., 2000ms)
- Minimum evaluation dataset size before promoting a model?
- Required precision/recall floor for extraction tasks?
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.
- yesterday First seen · 138 lines · 48 tokens per session scan A c87c92cc7a5d
context-add is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,225 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.
sensitive-logging-audit
Audit and fix sensitive-data exposure through Python runtime logging in openai-agents-python. Use when reviewing logging, print, warnings, stderr, traceback, MCP names, model or tool exceptions, redaction flags, or any diagnostic path that may retain user data.
hf-gguf-quant-jobs
Use when creating, monitoring, validating, or documenting low-memory Hugging Face Jobs or local runs that quantize split BF16/FP16 GGUF model repos into custom quant GGUF repos with skippy-quantize.
benchmark-tune
Use this skill when running, debugging, interpreting, or documenting mesh-llm benchmark tune model-serving throughput trials, including choosing ctx/batch/ubatch/mmap/mlock/speculative-decoding sweeps, running benchmark tune on local or SSH hosts, collecting JSON evidence, and applying tolerance-aware recommendations.…
hf-quant-and-layer-package-jobs
Use when running quantization of a BF16/FP16 GGUF repo and Skippy layer-package creation as one local or Hugging Face Jobs workflow, publishing both artifacts to Hugging Face.
hf-bf16-gguf-conversion-jobs
Use when converting Hugging Face SafeTensors checkpoints into split BF16 GGUF model repos with skippy-quantize on Hugging Face Jobs or a local machine, then publishing the artifact to Hugging Face.