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 skills add zpower426/datapowers --skill writing-analysis-plansgit 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/writing-analysis-plans)<a href="https://agentmods.dev/skills/zpower426/datapowers/writing-analysis-plans"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/writing-analysis-plans/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zpower426/datapowers/writing-analysis-plans"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/writing-analysis-plans.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01331 |
| Opus 5 | $0.00017 | $0.00665 |
| Sonnet 5 | $0.00007 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
writing-analysis-plans 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 10d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Analysis Plans
Convert an approved analytical design into a detailed, executable plan with no placeholders, no ambiguity, and no implicit context.
Checklist
- Load the design doc — read the spec from
docs/datapowers/specs/ - Identify all work streams — EDA, validation, feature engineering, modeling, evaluation, reporting
- Decompose into tasks — 15-30 minutes each, independently executable
- Write each task with full specificity — no placeholders, no "similar to above"
- Add verification step to every task — how to confirm completion
- Self-review the plan — check coverage, placeholder scan, task size
- Save plan —
docs/datapowers/plans/YYYY-MM-DD-<topic>-plan.md - User reviews plan — confirm before execution begins
Task Decomposition Rules
Every task must specify:
- Exact files or data to read
- Exact outputs to produce (file names, variable names)
- Exact code or commands (no "write code to do X")
- Verification — what to run/check to confirm success
❌ Bad Task
Task 3: Feature engineering
- Create features for the churn dataset
- Handle missing values
- Encode categoricals
This is useless. An agent cannot execute this without guessing.
✅ Good Task
Task 3: Numeric feature preprocessing
Files: data/train.csv, data/test.csv
Steps:
1. Load X_train from data/train_features.csv (saved in Task 2)
2. For columns ['age', 'tenure_months', 'monthly_charges']:
- Clip outliers at [Q1 - 3×IQR, Q3 + 3×IQR] using training set quantiles
- Impute with median (fit on X_train, transform X_test)
- Apply StandardScaler (fit on X_train, transform X_test)
3. Save fitted imputer to artifacts/imputer_numeric.pkl
4. Save fitted scaler to artifacts/scaler_numeric.pkl
5. Save transformed training features to data/X_train_numeric.csv
6. Save transformed test features to data/X_test_numeric.csv
Verification:
- Run: python -c "import pandas as pd; df=pd.read_csv('data/X_train_numeric.csv'); print(df.isnull().sum())"
- Expected: all zeros (no nulls after imputation)
- Run: python -c "import pandas as pd; df=pd.read_csv('data/X_train_numeric.csv'); print(df.describe())"
- Expected: means near 0, stds near 1 (after scaling)
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.
- 10d ago First seen · 159 lines · 34 tokens per session scan A eb0768bf0309
writing-analysis-plans is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,331 once invoked, about $0.0002 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
peer-conversation
A structured, multi-turn discussion between the main coding agent and one or more other AI assistants about a task.
kimi-peer-writer
A peer-work session in which Kimi writes and Claude acts as a second participant. It supports repeated turns, escalation, review, checking, and a decision about whether to record or implement a result.
archgate
An architecture review method that evaluates a proposed system design or technology change across seven qualities.
pack-new
Create a new Pack — guided flow through SPF: choose domain, name Pack, scaffold structure, fill roadmap.
apply-captures
A review process for extraction reports marked as waiting for review. It lets a person accept, reject, or defer each proposed item and records the decision.
bottleneck-pick
A constraint-analysis skill that finds the main bottleneck, the part of a workflow limiting overall progress, for a specific project or work plan.