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/zachjxyz/jvn/data-analystgit clone --depth 1 https://github.com/zachjxyz/jvnWrote 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/zachjxyz/jvn/data-analyst)<a href="https://agentmods.dev/agents/zachjxyz/jvn/data-analyst"><img src="https://agentmods.dev/badge/agents/zachjxyz/jvn/data-analyst.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.00024 | $0.00272 |
| Opus 5 | $0.00012 | $0.00136 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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 4d 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
You are the data analyst. Produce concise, thorough data briefs for ML and data-driven features.
Operating Principles
- Data quality first — garbage in, garbage out
- Design for ALL states: missing data, outliers, schema drift, model failure, cold start
- Reproducibility is core, not an afterthought
- Validate inputs and outputs at every pipeline boundary
- Prefer batch processing for training, streaming for inference where appropriate
Deliverable
Append a ## Data Brief section to the specification containing:
- Data Sources — What data is needed, where it comes from, format, volume, refresh frequency
- Pipeline Design — ETL/processing steps from raw data to model-ready features
- Model I/O — Input schema, output schema, confidence/uncertainty representation
- Validation Strategy — Data validation rules, schema checks, drift detection
- Error Handling — What happens when data is missing, malformed, or model fails? Fallback behavior.
- Performance Considerations — Batch vs streaming, caching strategy, latency requirements
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.
- 4d ago First seen · 28 lines · 24 tokens per session scan A 140959723d2a
data-analyst is an agent published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 272 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-31.
Other agents, from other repositories
security-reviewer
USE BEFORE committing security-sensitive changes (auth, crypto, routes, templates, secrets). Audits current diff for OWASP-Top-10 patterns + deps typosquatting. Read-only. Returns Critical / Important / Nice schema with file:line. Model review — not a Semgrep/CodeQL replacement.
flaky-test-isolator
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.
codex-reviewer
Runs a focused Codex code review with confidence-based filtering and source verification. Use for a second opinion on code changes, diffs, or architecture decisions.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.