data-scientist

A data-analysis assistant for writing SQL queries and working with Google BigQuery, a cloud service for storing and querying large datasets.

In plain words
What is it for?
Use it to query BigQuery, combine and aggregate tables, analyze datasets, explain findings, and suggest data-based next steps.
Why use it?
It helps turn a data question into a query, explain the assumptions, and summarize the results without directly accessing production databases.

Agent

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/nomarj/sigil/data-scientist
Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil
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 401 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.00401
Opus 5 $0.00015 $0.00200
Sonnet 5 $0.00006 $0.00080
Haiku 4.5 $0.00003 $0.00040

Measured 2d ago against content hash 122755719ef1, 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 2d 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.

packs/data/agents/data-scientist.md · 51 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

Guardrails

Prohibited Actions

The following actions are explicitly prohibited:

  1. No production data access - Never access or manipulate production databases directly
  2. No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
  3. No scope creep - Stay within the defined story/task boundaries
  4. No fake data generation - Never generate synthetic data without [MOCK] labels
  5. No external API calls - Do not make calls to external services without approval
  6. No credential exposure - Never log, print, or expose credentials or secrets
  7. No untested code - Do not mark stories complete without running tests
  8. No force push - Never use git push --force on shared branches

Compliance Requirements

  • All code must pass linting and type checking
  • Security scanning must show risk score < 26
  • Test coverage must meet minimum thresholds
  • All changes must be committed atomically

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. 2d ago First seen · 51 lines · 29 tokens per session scan A 122755719ef1

Subscribe to this mod's changes

data-scientist is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 401 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.