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/joris887/exosuit/quality-checknpx skills add joris887/exosuit --skill quality-checkgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/quality-check)<a href="https://agentmods.dev/skills/joris887/exosuit/quality-check"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/quality-check.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.00017 | $0.00889 |
| Opus 5 | $0.00009 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
quality-check 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quality-check
Running quality gates: $ARGUMENTS
1. Parse Flags
Extract check selection from $ARGUMENTS:
| Flag | Dispatches |
|---|---|
--code |
/code-quality |
--tests |
/test-validator |
--security |
/security-audit |
--architecture |
/architecture-check |
--performance |
/performance-check |
--all |
All 5 checks above |
2. Apply Profile Defaults
If NO flags are provided, read the project profile from the **Profile:** line in CLAUDE.md and apply defaults:
| Profile | Default Checks |
|---|---|
| lean | --code (lint + complexity only) |
| standard | --code --tests --security |
| strict | --all plus integration-tester agent |
If the profile is not set or not recognized, default to standard behavior.
3. Run Quality-Gate-Sequence First
Before dispatching agent skills, run the quality-gate-sequence micro-component from .claude/prompts/quality-gate-sequence.md — this runs lint, typecheck, and tests from CLAUDE.md Commands. These are fast, deterministic checks that catch issues before the more expensive agent analysis.
HARD GATE: If tests fail, stop here. Do not dispatch agent skills on failing code.
4. Dispatch Selected Checks
Dispatch each selected check as a parallel Task agent. Each invokes the corresponding skill:
For each selected check:
Launch Agent (subagent_type: general-purpose) with prompt:
"Run /<skill-name> on the current codebase. Return a structured report."
Run all selected checks in parallel for efficiency. Wait for all to complete.
5. Unified Report
Combine results from all dispatched checks into a single report:
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 · 101 lines · 17 tokens per session scan A dc7bdce4a635
quality-check is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 16d ago), licensed MIT. It adds 17 tokens to every session and 889 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
moai-workflow-tdd
Test-Driven Development workflow specialist using RED-GREEN-REFACTOR cycle for test-first software development. Use when developing new features from scratch or when behavior specification drives implementation.
hns-oss-docs-verify
Mandatory verify recipe for the oss-docs harness — the runnable exit gate every specialist executes before returning: warning-free hugo build, sitemap existence, URL-blacklist grep, Mermaid LR/RL direction grep, 4-locale file-existence and section-count parity, README 4-file heading parity, and body-emoji scan. All…
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
moai-foundation-quality
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
moai-workflow-loop
Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.
moai-workflow-testing
Use when writing tests, measuring coverage, or running characterization, performance, or PR-review QA. Comprehensive specialist combining DDD testing, characterization tests, performance profiling, and TRUST 5 quality-assurance validation.