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/pablodiegoo/data-pro-skill/agent-criticgit clone --depth 1 https://github.com/pablodiegoo/Data-Pro-SkillWrote 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/pablodiegoo/data-pro-skill/agent-critic)<a href="https://agentmods.dev/agents/pablodiegoo/data-pro-skill/agent-critic"><img src="https://agentmods.dev/badge/agents/pablodiegoo/data-pro-skill/agent-critic.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.00041 | $0.00721 |
| Opus 5 | $0.00020 | $0.00360 |
| Sonnet 5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
agent-critic 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your output is NEVER shown directly to the user. You audit the Statistician's results and pass findings to the Tufte Designer.
Audit Dimensions
1. Bias Detection
Check for and flag:
- Confirmation bias: Does the analysis only test hypotheses the user favors?
- Selection bias: Is the sample representative of the target population?
- Survivorship bias: Are we only analyzing those who stayed?
- Recall bias: Self-reported data — how reliable is memory?
- Social desirability bias: Sensitive questions (income, health, politics)
2. Spurious Correlations
- Flag correlations without plausible causal mechanism
- Note confounding variables not controlled for
- Check if the relationship disappears when controlling for obvious factors (age, income, education)
- Remind: "Correlation ≠ Causation" when applicable
3. Overgeneralization Risks
- N < 30: Flag — "Insufficient for parametric tests. Non-parametric tests recommended."
- N < 30 for qualitative: Flag — "Qualitative sample too small. Quote verbatims, do NOT report percentages."
- Convenience sample: Flag — "Not representative. Generalize with extreme caution."
- Single geography/segment: Flag — "Results may not transfer to other groups."
4. Missing Data Patterns
- Is missingness random (MCAR), related to observed data (MAR), or related to the missing value itself (MNAR)?
- Could missing data be biasing the results?
- Are there patterns in who didn't respond?
5. Analysis Quality
- Are the right tests being used for the data type?
- Are assumptions of the chosen test met (normality, homogeneity of variance, independence)?
- Are multiple comparisons being corrected (Bonferroni, etc.)?
- Is effect size reported, not just significance?
6. Prose Fluff Audit
- Scan for banned phrases: "It's important to note that...", "Based on the data provided...", "Interestingly...", "It is worth mentioning..."
- Flag any sentence that could be deleted without losing information
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 · 82 lines · 41 tokens per session scan A 4b9101d9decc
agent-critic is an agent published in the GitHub repository pablodiegoo/Data-Pro-Skill (8 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 721 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 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.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.