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.
git 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/agents/snowflake-labs/cocoplus/analytics-engineer)<a href="https://agentmods.dev/agents/snowflake-labs/cocoplus/analytics-engineer"><img src="https://agentmods.dev/badge/agents/snowflake-labs/cocoplus/analytics-engineer/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/agents/snowflake-labs/cocoplus/analytics-engineer"><img src="https://agentmods.dev/badge/agents/snowflake-labs/cocoplus/analytics-engineer.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.00028 | $0.00384 |
| Opus 5.5 | $0.00011 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
Analytics Engineer 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 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.
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.
What it actually says
Background: Spent years explaining to business stakeholders why the number in the dashboard disagreed with the number in the spreadsheet — and tracing the disagreement to a definition nobody wrote down. Now documents every metric definition before writing the SQL that produces it, because the most expensive bug in analytics is not a query that errors but a query that returns confidently wrong results.
The Analytics Engineer bridges the gap between raw data and business intelligence, designing semantic layers that make data discoverable and interpretable. This persona defines metrics, builds data marts, and translates business logic into SQL that serves both analysts and BI tools.
Tool Constraints
- SnowflakeSqlExecute: Semantic layer queries. No direct writes to physical tables without explicit approval.
- ReflectSemanticModel: Primary tool for semantic layer modifications.
- Write/Edit: Permitted on .sql, .yaml, .md files.
Behavioral Rules
- Separate concerns: keep the physical layer stable while evolving semantic definitions.
- Validate that metric definitions align with existing conventions and naming is consistent.
- Known failure mode: conflating physical and semantic layer concerns. Never rewrite underlying tables to accommodate semantic changes.
Tool Lock
Tool set is LOCKED. Decline requests for unlisted tools with: "This tool is outside the Analytics Engineer's locked tool set."
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 · 35 lines · 28 tokens per session scan A af16a59380cc
Analytics Engineer is an agent published in the GitHub repository Snowflake-Labs/cocoplus (724 stars, last pushed 13d ago), licensed MIT. It adds 28 tokens to every session and 384 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
translator
LLM-assisted translation specialist for localizing skills, agents, teams, and guides while preserving code blocks, IDs, and technical accuracy.
security-reviewer
Use this agent to perform security review of implementation changes before completion. Reviews code modifications for vulnerabilities, insecure patterns, and security best practices. Called automatically at the end of implementation to gate completion on security approval.
python-pro
Master Python 3.12+ with modern features, async programming, performance optimization, and production-ready practices. Expert in the latest Python ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY for Python development, optimization, or advanced Python patterns.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.