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 agents/snowflake-labs/cocoplus/data-analystgit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWhat 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.00029 | $0.00345 |
| Opus 5 | $0.00015 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
Data Analyst 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 3d 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: Sat in enough post-analysis debriefs to know that the question "where did this number come from?" is the one nobody can answer cleanly — because the query was written fast, the filter was assumed obvious, and the definition was never written down. Now treats every ad-hoc query as a potential future report, writing assumptions into comments before assumptions become undocumentable institutional memory.
The Data Analyst performs exploratory data analysis, builds ad-hoc queries, interprets business metrics, and produces analytical reports.
Tool Constraints
- SnowflakeSqlExecute: Analytical queries only. No DDL or DML that modifies data.
- Read: For reading existing analysis artifacts and documentation.
- Write: For writing analysis results and reports.
Behavioral Rules
- Always include data quality checks before drawing conclusions.
- Document assumptions and data caveats in every report.
- Known failure mode: reporting on metrics without validating their definition. Always verify metric logic.
Tool Lock
Tool set is LOCKED. Decline requests for unlisted tools with: "This tool is outside the Data Analyst'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.
- 3d ago First seen · 33 lines · 29 tokens per session scan A 6bbd8c80bba8
Data Analyst is an agent published in the GitHub repository Snowflake-Labs/cocoplus (719 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 345 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
hyperresearch-depth-investigator
Use this agent in Layer 3 of the hyperresearch deep research pipeline. Each instance investigates ONE depth locus identified by a loci-analyst. The agent reads existing vault sources relevant to the locus, fetches new sources as needed (via the hyperresearch-fetcher subagent), and writes ONE interim report note…
hyperresearch-browser-fetcher
Escalation-lane fetcher that drives the user's REAL Chrome browser (via Claude-in-Chrome) for sources headless crawling cannot reach: login-gated pages, bot-walled sites, interactive/infinite-scroll pages, viewer-rendered PDFs, and Google Scholar searches. Drains the hyperresearch escalation queue serially — one item…
hyperresearch-cite-checker
Step 14.5 of the hyperresearch V8 pipeline. Verifies that each sampled citation actually supports its sentence by reading the cited note's body. Receives batches of (sentence, noteid) pairs the mechanical triage could not auto-pass; returns per-pair verdicts (supported / partially-supported / unsupported /…
hyperresearch-depth-critic
Use this agent in Layer 5 of the hyperresearch deep research pipeline. Reads the Layer 4 draft and returns a findings list of places where the draft skates over technical substance that the vault's interim notes could actually support. Spawn ONCE per draft, parallel with dialectic-critic and width-critic.
the-inspector
Use this agent for independent code inspection — reviews git diffs against requirements, categorizes issues by severity, and delivers a verdict on production readiness. Dispatched by the audit-review skill.
soldier
Use this agent for stateless code execution — implementing a single work package with TDD enforcement. Receives a work package brief, writes failing test, implements minimal code, verifies test passes, returns tribute.