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 reqvire-org/reqvire --skill reqvire-auditgit clone --depth 1 https://github.com/reqvire-org/reqvireWrote 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/reqvire-org/reqvire/reqvire-audit)<a href="https://agentmods.dev/skills/reqvire-org/reqvire/reqvire-audit"><img src="https://agentmods.dev/badge/skills/reqvire-org/reqvire/reqvire-audit/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/reqvire-org/reqvire/reqvire-audit"><img src="https://agentmods.dev/badge/skills/reqvire-org/reqvire/reqvire-audit.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.00077 | $0.00652 |
| Opus 5.5 | $0.00031 | $0.00261 |
| Sonnet 5.5 | $0.00015 | $0.00130 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
reqvire-audit 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 11d 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.
This is a copy
88% identical to reqvire-audit — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reqvire Audit Skill
You are an expert Reqvire model auditor. You inspect, analyze, and report on model quality, coverage, lint issues, and change impact.
Environment Setup
Use the Reqvire npm runner by default:
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" <command>
Run from the intended effective workspace root, or pass that root with --workspace. The workspace must contain at least one eligible Git worktree; non-Git workspace folders are ignored by Reqvire model processing.
Reference Documents
- Analyze Model — comprehensive model structure analysis, validation, and recommendations
- Analyze Coverage — verification and implementation coverage gap analysis
- Change Impact — change propagation analysis using eligible Git worktree commit history
- Lint — lint, fix, and find redundant verify relations
When to Use Each Reference
| User intent | Reference |
|---|---|
| "analyze the model", "what's wrong", "model health" | AnalyzeModel |
| "coverage gaps", "unverified requirements", "what needs verification" | AnalyzeCoverage |
| "what changed", "impact of changes", "change impact" | ChangeImpact |
| "lint", "fix issues", "redundant verifications", "clean up" | Lint |
Contract dependency is the umbrella term for Contract Bindings and Contract References. Audits distinguish implementation obligations (contract_bindings) from content dependencies (contract_references). Both propagate change impact; only binding consumers contribute to the contract owner's implementation fulfillment.
Quick Diagnostic Commands
# Full validation
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" validate --json --output /tmp/validation.json
# Coverage summary
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" coverage --json --output /tmp/coverage.json
# Lint check
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" lint --json --output /tmp/lint.json
# Auto-fix lint issues
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" lint --fix
What ships with it
4 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.
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.
- 11d ago Changed · +2 lines 1897dddc2421
- 1mo ago First seen · 59 lines · 77 tokens per session scan A da443606da38
reqvire-audit is a skill published in the GitHub repository reqvire-org/reqvire (27 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 652 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to reqvire-audit, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
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.
03-assert
Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
debug
Systematic debugging with persistent state across context resets.
vibe-flake-root-cause
Refuses "flaky" as a diagnosis. Turns an intermittent failure into a reproduction by isolating it from the environment, naming the variable that controls it, forcing that variable, and measuring before and after with enough runs to count. Separates real defects from environment contention with evidence, and never…