Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pedrohcgs/Claude-Mininpx agentmods add skills/pedrohcgs/claude-mini/qa-quartoWrote 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/pedrohcgs/claude-mini/qa-quarto)<a href="https://agentmods.dev/skills/pedrohcgs/claude-mini/qa-quarto"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-mini/qa-quarto.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.00043 | $0.02551 |
| Opus 5 | $0.00022 | $0.01275 |
| Sonnet 5 | $0.00009 | $0.00510 |
| Haiku 4.5 | $0.00004 | $0.00255 |
Grade A, and why
qa-quarto 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 7d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adversarial Quarto vs Beamer QA Workflow
Compare Quarto HTML slides against their Beamer PDF benchmark using an iterative critic/fixer loop.
Philosophy: The Beamer PDF is the gold standard. The Quarto translation must be at least as good in every dimension. The critic assumes Quarto is guilty until proven innocent.
Workflow Overview
┌─────────────────────────────────────────────────────────────┐
│ /qa-quarto LectureX │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ Phase 0: Pre-flight Verification │
│ • Verify Beamer PDF exists and is recent │
│ • Verify Quarto HTML exists and is recent │
│ • Check file freshness (modification times) │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ Phase 1: Initial Audit (quarto-critic agent) │
│ • Compare Beamer vs Quarto comprehensively │
│ • Check hard gates (overflow, content parity, etc.) │
│ • Produce detailed report with actionable fixes │
│ • May delegate to sub-agents (e.g. slide-auditor) │
└─────────────────────────────────────────────────────────────┘
│
▼
┌───────────────┐
│ Verdict? │
└───────────────┘
/ \
APPROVED NEEDS REVISION / REJECTED
│ │
▼ ▼
┌─────────────────────┐ ┌─────────────────────────────────────┐
│ Done! │ │ Phase 2: Fix Cycle (quarto-fixer) │
│ Save final report │ │ • Apply critical issues first │
│ Celebrate 🎉 │ │ • Then major, then minor │
└─────────────────────┘ │ • Re-render slides │
│ • Verify fixes compiled │
└─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────┐
│ Phase 3: Re-Audit (quarto-critic) │
│ • Check if fixes worked │
│ • Update verdict │
│ • Identify any new issues │
└─────────────────────────────────────┘
│
▼
┌───────────────┐
│ Verdict? │
└───────────────┘
/ \
APPROVED NEEDS REVISION
│ │
▼ │
┌─────────────────┐ │
│ Done! │ │
└─────────────────┘ │
│
┌─────────┘
│ (Loop back to Phase 2)
│ Max 5 iterations
▼
┌─────────────────────────┐
│ After 5 rounds: │
│ Escalate to user with │
│ remaining issues │
└─────────────────────────┘
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.
- 7d ago First seen · 325 lines · 43 tokens per session scan A d9336fb74498
qa-quarto is a skill published in the GitHub repository pedrohcgs/Claude-Mini (11 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 2,551 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
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.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.