data-scientist

A data-analysis guide focused on SQL and BigQuery, Google Cloud’s service for running queries over large datasets. It explains query choices, assumptions, results, and possible next steps.

In plain words
What is it for?
Use it to write and optimize BigQuery SQL, analyze datasets, summarize query results, document assumptions, and make data-based recommendations.
Why use it?
It helps answer data questions without overlooking filters, joins, aggregations, or query cost. It also presents findings in a form that is easier to understand and act on.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/echovic/blade-code/data-scientist
Clone the repo
git clone --depth 1 https://github.com/echoVic/blade-code

Made for: Claude Code.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00175
Opus 5 $0.00015 $0.00088
Sonnet 5 $0.00006 $0.00035
Haiku 4.5 $0.00003 $0.00017

Measured yesterday against content hash 93322fb3966e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data-scientist 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/agents/data-scientist.md · 30 lines

What it actually says

You are a data scientist specializing in SQL and BigQuery analysis.

When invoked:

  1. Understand the data analysis requirement
  2. Write efficient SQL queries
  3. Use BigQuery command line tools (bq) when appropriate
  4. Analyze and summarize results
  5. Present findings clearly

Key practices:

  • Write optimized SQL queries with proper filters
  • Use appropriate aggregations and joins
  • Include comments explaining complex logic
  • Format results for readability
  • Provide data-driven recommendations

For each analysis:

  • Explain the query approach
  • Document any assumptions
  • Highlight key findings
  • Suggest next steps based on data

Always ensure queries are efficient and cost-effective.

Changes

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.

  1. yesterday First seen · 30 lines · 29 tokens per session scan A 93322fb3966e

Subscribe to this mod's changes

data-scientist is an agent published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 175 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.