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 skills/rbah31/claude-code-workflow/data-analysisnpx skills add rbah31/claude-code-workflow --skill data-analysisgit clone --depth 1 https://github.com/rbah31/claude-code-workflowWhat 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.00119 | $0.00996 |
| Opus 5 | $0.00060 | $0.00498 |
| Sonnet 5 | $0.00024 | $0.00199 |
| Haiku 4.5 | $0.00012 | $0.00100 |
Grade A, and why
data-analysis 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Analysis
You answer data questions by fetching real data, not guessing. This skill gives you the tools and query patterns to investigate.
Read config.json in this skill directory for data source configuration.
If it doesn't exist, ask the user to set it up (see Setup section).
Data sources
Check scripts/ for helper functions specific to this project. These scripts
encode domain knowledge (which tables to join, which event names to use,
how to dedupe) so you don't have to figure it out each time.
If helper scripts exist, compose them — import and combine rather than
rewriting from scratch. Generate new investigation scripts on the fly that
use the helpers. Save useful investigation scripts in scripts/ for reuse.
If no helpers exist yet, write the query directly, then extract reusable parts into helpers for next time.
Common investigation patterns
Adapt these to the project's actual data stack:
"What happened on [date]?" — Compare the target day against the previous day and same day last week. Look at volume, error rate, and key conversion points.
"Why did [metric] drop?" — Segment by the obvious dimensions first (source, device, geography, plan tier). The segment where the drop is concentrated tells you where to dig.
"Is [thing] working?" — Define "working" as a measurable assertion. Query the data, check the assertion, report the result.
"Compare A vs B" — Pull the same metrics for both cohorts. Flag differences that exceed normal variance. Note sample sizes.
How to query
Use whatever the project provides — adapt to the stack:
- SQL databases: Write queries directly or use helper scripts
- AWS CloudWatch: Use
aws cloudwatch get-metric-statistics - DynamoDB: Use
aws dynamodb querywith appropriate key conditions - Event systems: Use the project's event query library
- Logs: Use
aws logs filter-log-eventsor grep on log files - Third-party APIs: Stripe dashboard data, Discord analytics, etc.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 124 lines · 119 tokens per session scan A 092f666a7840
data-analysis is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 996 once invoked, about $0.0006 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 skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-payments
Agent skill for payments - invoke with $agent-payments.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…