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/zpower426/datapowers/using-datapowersnpx skills add zpower426/datapowers --skill using-datapowersgit clone --depth 1 https://github.com/zpower426/datapowersWrote 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/skills/zpower426/datapowers/using-datapowers)<a href="https://agentmods.dev/skills/zpower426/datapowers/using-datapowers"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/using-datapowers.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.1 | $0.00020 | $0.00394 |
| Opus 5 | $0.00010 | $0.00197 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
using-datapowers 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 5d 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
Using Datapowers
The Workflow
Datapowers enforces a disciplined analytical workflow:
- brainstorming → Hypothesis-first design.
- writing-analysis-plans → Task decomposition.
- data-profiling → Context injection without raw data.
- executing-plans → Two-stage review for every task.
- leakage-guard → Temporal and preprocessing audit.
- test-driven-data-science → Three-layer assertions.
- verification-before-delivery → Evidence-based completion.
Triggering Skills
| Skill | Trigger Keywords |
|---|---|
brainstorming |
"Analyze", "Hypothesis", "Design spec" |
analysis-manifest |
Session start, "Where are we?", "Resume analysis", after brainstorming completes |
data-profiling |
"What's in the data?", "Profile", "New dataset" |
leakage-guard |
"Feature window", "Split", "Leakage" |
test-driven-data-science |
"Before training", "Assertion", "Drift" |
executing-plans |
"Start tasks", "Follow plan" |
requesting-statistical-review |
"Audit results", "Significance" |
verification-before-delivery |
"Done", "Fixed", "Complete" |
writing-data-skills |
"New skill", "Add skill", "Contribute skill" |
The Philosophy
- Statistical Integrity > Model Metrics
- Validation Before Implementation
- Evidence over Assertions
- Isolated Subagents with High-Density Profiles
Ready? Invoke brainstorming to begin your analysis.
What ships with it
2 files 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.
- 5d ago First seen · 42 lines · 20 tokens per session scan A c979add09d36
using-datapowers is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 394 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
fba-simulator
Run Flux Balance Analysis (FBA) and related constraint-based simulations using COBRApy. Covers standard FBA, parsimonious FBA (pFBA), Flux Variability Analysis (FVA), loopless FBA, gene/reaction knockouts, and carbon source swapping. Outputs flux distributions and CSV files.
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
gsmm-validator
Validate a COBRApy genome-scale metabolic model for mass/charge balance, stoichiometric consistency, biomass producibility, dead-end metabolites, thermodynamic loops, and GPR rule formatting. Outputs a structured validation report with errors and warnings.
gsmm-builder
Build or load a genome-scale metabolic model (GSMM) using COBRApy. Covers loading from BIGG, constructing minimal models from scratch, setting medium constraints, and exporting validated .json model files.
stat-result-validator
Validate statistical research outputs for formulation quality, method-to- problem alignment, theory presence, experimental evidence, fair comparison, artifact completeness, and final-claim consistency.