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/joaquimscosta/arkhe-claude-plugins/quality-stacknpx skills add joaquimscosta/arkhe-claude-plugins --skill quality-stackgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/quality-stack)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/quality-stack"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/quality-stack.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.00148 | $0.01989 |
| Opus 5 | $0.00074 | $0.00994 |
| Sonnet 5 | $0.00030 | $0.00398 |
| Haiku 4.5 | $0.00015 | $0.00199 |
Grade A, and why
quality-stack 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 6d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Stack
Scan a project's build configuration across JVM, Android, Node.js, and Python ecosystems, cross-reference against curated research documents, and assist with tool setup.
Pre-flight
- Run the orchestrator — it auto-detects ecosystems:
python3 <skill-path>/scripts/scan_project.py <project-root> - If
"error": "no_ecosystem_detected", checknearby_project_filesfor subproject paths. - Monorepo? — use
--recursiveor--ecosystemto force a specific scanner:python3 <skill-path>/scripts/scan_project.py --recursive <project-root> python3 <skill-path>/scripts/scan_project.py --ecosystem node <project-root> - Legacy (JVM only) —
scan_tooling.pystill works as a backwards-compatible wrapper.
Two-Phase Workflow
Phase 1: Recommend
-
Run the scanner on the project root (see Pre-flight above).
-
Fetch research documents via WebFetch — only for detected ecosystems:
Android (when
ecosystemscontains"android"):https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/android-ecosystem-tooling.md https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/android-testing-ecosystem.mdJVM (when
ecosystemscontains"jvm"):https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/jvm-quality-tools-evaluation.md https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/kotlin-spring-boot-testing-ecosystem.mdNode.js (when
ecosystemscontains"node"):https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/node-quality-tools-evaluation.mdPython (when
ecosystemscontains"python"):https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/python-quality-tools-evaluation.mdCross-cutting (always):
https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/cross-cutting-devtools-evaluation.md
What ships with it
11 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.
- EXAMPLES.md 28 KB
- scripts/scan_android.py 30 KB runs code
- scripts/scan_cross_cutting.py 18 KB runs code
- scripts/scan_jvm.py 28 KB runs code
- scripts/scan_node.py 19 KB runs code
- scripts/scan_project.py 13 KB runs code
- scripts/scan_python.py 24 KB runs code
- scripts/scan_tooling.py 485 B runs code
- scripts/shared.py 2.3 KB runs code
- TROUBLESHOOTING.md 15 KB
- WORKFLOW.md 38 KB
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.
- 6d ago First seen · 167 lines · 148 tokens per session scan A ce5b983feead
quality-stack is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 23d ago), licensed MIT. It adds 148 tokens to every session and 1,989 once invoked, about $0.0007 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-30.
Other skills, from other repositories
test-writer
Generate comprehensive tests including unit, integration, and property-based tests.
dev-full-auto
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
dev-qa
Run the project's own tests, linter, type checker and build, and report what actually failed.
verify
Verify phase — evidence-based validation with sentinel dispatch and pass/fail scorecard.
test-driven-development
Use when implementing any feature or bugfix, in any language or framework, before writing implementation code — write the test first, watch it fail, then write minimal code to pass. Covers the red-green-refactor loop, test-quality principles, rationalization counters, and test-layer selection.
benchmark
Compare Claude Code output with full config vs minimal config using standardized tasks per stack.