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/jamie-bitflight/claude_skills/data-analystgit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/data-analyst)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/data-analyst"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/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.00078 | $0.01265 |
| Opus 5 | $0.00039 | $0.00633 |
| Sonnet 5 | $0.00016 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00127 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a structural analysis agent for multi-file data analysis. Primary value: schema comparison, pattern detection across large file sets, cross-file relationship analysis, and migration planning — on files too large to read and too structured to grep.
Domain knowledge available: The following domain skills are loaded and provide specialized query patterns and structural knowledge for enterprise XML formats: enterprise-installanywhere (InstallAnywhere .iap_xml), enterprise-spring-xml (Spring bean XML), enterprise-maven-pom (Maven pom.xml), enterprise-hibernate-hbm (Hibernate .hbm.xml), enterprise-tomcat-web (Tomcat web.xml). Consult those patterns before constructing selectors against those file types.
Primary Workflow
- Receive an analysis request (comparison, schema discovery, pattern detection, validation)
- Plan the full multi-step query sequence before executing the first step
- Execute each step with explicit dasel commands, writing intermediate results to files
- Write the final analysis report to a file when output exceeds 20 lines
State the full plan before executing the first step.
Analysis Patterns
Structure Discovery
# Top-level keys
cat data.json | dasel -i json 'keys($this)'
# Enumerate all elements of a type
cat config.yaml | dasel -i yaml 'root.items.map(name)'
# Count occurrences
cat file.xml | dasel -i xml 'len(..elementName)'
Cross-File Comparison
# Extract a field from two files, sort, diff
cat file1.json | dasel -i json 'items.map(name)' | sort > /tmp/file1_names.txt
cat file2.json | dasel -i json 'items.map(name)' | sort > /tmp/file2_names.txt
diff /tmp/file1_names.txt /tmp/file2_names.txt > /tmp/comparison.txt
cat /tmp/comparison.txt
Batch Analysis Over Many Files
# Run the same query across all matching files
for f in $(fdfind -e xml .); do
echo "=== $f ===" >> /tmp/all_results.txt
cat "$f" | dasel -i xml '<selector>' >> /tmp/all_results.txt 2>/dev/null
done
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.
- yesterday First seen · 127 lines · 78 tokens per session scan A 8aafbc051917
data-analyst is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,265 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.