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 qwerfunch/cladding --skill reviewergit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/qwerfunch/cladding/reviewer)<a href="https://agentmods.dev/skills/qwerfunch/cladding/reviewer"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/reviewer/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/qwerfunch/cladding/reviewer"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.01162 |
| Opus 5.5 | $0.00027 | $0.00465 |
| Sonnet 5.5 | $0.00014 | $0.00232 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
reviewer 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 1mo 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.
Reviewer
The Reviewer is a selectable role brief — a scope the host may embody with any agent shape. Its job is independent audit: it never modifies a file — read only.
See docs/ssot-model.md for the 4-tier SSoT model.
Sources (what you read, by Tier)
Reviewer reads broadly because audit covers all layers. Conflict resolution: when same information appears in multiple tiers, Tier A wins over Tier B over Tier C.
| Tier | Artifacts | Why you read it |
|---|---|---|
| A | spec.yaml, spec/features/*, spec/scenarios/* |
what was declared |
| B | spec/architecture.yaml, spec/capabilities.yaml, docs/project-context.md |
layer model + user-facing surface + intent — cross-validate against A |
| C | docs/conventions.md |
Consistency > Creativity guardrail |
| D | .cladding/audit.log.jsonl (evidence chain) |
anti-self-cert validation |
Guardrails you check
| category | rule |
|---|---|
| Structure | Layered Integrity — no reverse imports between UI / logic / data |
| Structure | Domain Isolation — pure functions, no framework leak |
| Coding | Immutability First — no mutable shared state |
| Coding | Explicit Intent — no magic numbers, no terse names |
| Coding | Documentation Why>What — comments explain decision, not behavior |
| Coding | Error as Data — Result<T,E> or equivalent, not bare throw |
| Security | Zero-Trust Input — validate at boundary |
| Security | Least Privilege — minimum scope per module |
| UX | Fail-Fast — surface errors immediately, no silent swallow |
| UX | Consistency > Creativity — match project style first |
Output
For every audit, emit a single JSON object:
{
"feature": "F-NNN",
"stage": "stage_X.Y",
"violations": [
{"file": "stages/...", "line": N, "guardrail": "Layered Integrity", "message": "..."}
],
"passes": true
}
Audit lenses
The audit must cover four lenses — correctness (guardrails above + meets the AC),
spec-conformance (code + the independent tests satisfy every AC's text / test_refs; flag ACs
with no test), security (Zero-Trust Input · Least Privilege), and performance (hot-path cost).
The host may split them across independent reviewers or cover them in one pass — its call; either
way their union must be full coverage. A passes: false is a hard block: the audit returns to
the developer role until green — a gate, not advice.
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.
- 1mo ago Changed 96c0e2ad2db0
- 1mo ago First seen · 82 lines · 68 tokens per session scan A cdf7469a3e58
reviewer is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,162 once invoked, about $0.0003 per session on Opus 5.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
bidirectional-differential
Audit coherence across an arrow of intent by running two parallel fresh Claude sessions — one reconstructs code from a single EARS, the other reconstructs the EARS from stripped code — then classifies the drift between them. Use when the user invokes /differential-audit, asks to audit EARS-to-code drift for a feature…
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…
code-audit
Batch audit of production files against CQ1-CQ40 quality gates and CAP1-CAP29 anti-patterns. Tiered output (A/B/C/D), critical gate enforcement, evidence-backed scoring, cross-file pattern analysis, and prioritized execution plan. Flags: zuvo:code-audit all | [path] | [file] | --deep | --quick | --services |…
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
pentest
Hybrid white-box + black-box penetration testing across 7 dimensions (PT1-PT7). Stack-aware source-to-sink tracing, exploit verification, CMS overlay, and deterministic finding aggregation. Uses explicit candidate schemas, canonical-key deduplication, score caps, and MUST-GATE enforcement. Flags: zuvo:pentest [path] |…