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 fabioc-aloha/Alex_Skill_Mall --skill universal-audit-patterngit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/universal-audit-pattern)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/universal-audit-pattern"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/universal-audit-pattern/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/fabioc-aloha/alex_skill_mall/universal-audit-pattern"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/universal-audit-pattern.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.00023 | $0.01139 |
| Opus 5 | $0.00012 | $0.00570 |
| Sonnet 5 | $0.00005 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
universal-audit-pattern 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal Audit Pattern
Category: Quality Time Saved: 4+ hours per audit Battle-tested: Yes — applied to docs, code, security, architecture
The Problem
You need to audit something — documentation accuracy, code quality, security compliance, architectural drift. You start checking things randomly, fix some issues, get distracted, lose track of what you've reviewed.
Why Ad-Hoc Audits Fail
- No systematic coverage — you miss things
- No severity ranking — you fix minor issues while critical ones wait
- No completion criteria — you don't know when you're done
- No reproducibility — next audit starts from scratch
The Rule
Inventory → Compare to Ground Truth → Severity-Classify → Fix All
This four-step pattern works for any domain where claims can drift from reality.
The Pattern
Step 1: Inventory
Create a complete list of items to audit. Be exhaustive.
## Inventory
| # | Item | Location | Status |
|---|------|----------|--------|
| 1 | Test count claim | README.md:45 | Pending |
| 2 | API endpoint list | docs/api.md | Pending |
| 3 | Version requirement | package.json | Pending |
| ... | ... | ... | ... |
Step 2: Compare to Ground Truth
For each item, verify against the authoritative source.
## Ground Truth Comparison
| # | Claim | Ground Truth | Match? |
|---|-------|--------------|--------|
| 1 | "47 tests" | `npm test` shows 89 | ❌ |
| 2 | "5 endpoints" | OpenAPI spec has 7 | ❌ |
| 3 | "Node 16+" | engines: ">=20" | ❌ |
Step 3: Severity-Classify
Prioritize by impact, not discovery order.
| Severity | Criteria | Example |
|---|---|---|
| Critical | Breaks functionality, security risk | Wrong API URL |
| High | Misleads users significantly | Wrong version requirements |
| Medium | Inaccurate but not harmful | Outdated feature list |
| Low | Cosmetic, minor | Typos in comments |
## Classified Findings
### Critical (fix immediately)
- [ ] #12: Security config example has hardcoded secret
### High (fix this sprint)
- [ ] #3: Version requirement mismatch
- [ ] #7: Deprecated API still documented
### Medium (fix when touched)
- [ ] #1: Test count outdated
- [ ] #2: Endpoint count wrong
### Low (backlog)
- [ ] #15: Typo in contributing guide
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 · 191 lines · 23 tokens per session scan A 8b17597c0b52
universal-audit-pattern is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,139 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-09-03.
Other skills, from other repositories
apply-fishbone-diagram
Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.
apply-early-intervention
Use when you detect early warning signals — technical debt accumulating, customer relationship cooling, team friction forming, process degrading — to intervene while the problem is still small and cheap, because intervention cost increases nonlinearly with delay.
diagnose-battery-charging-problem
Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.
diagnose-brake-system-problem
Use when experiencing brake warning signs such as noise, pulsation, pulling, soft pedal, or brake warning light to identify the fault before driving or seeking repair.
diagnose-check-engine-light
Use when a check engine light is illuminated and you need to identify the fault code, assess severity, and decide next steps.
diagnose-electrical-fault
Use when a vehicle has a blown fuse, inoperative accessory, warning light, or intermittent electrical failure — applying a systematic test sequence (visual, OBD-II codes, voltage/continuity testing) to isolate the fault to a specific component or circuit without replacing parts blindly.