audit

audit is a skill for Claude Code, Codex from Wondermonger-daydreaming/claude-skills-library. It costs 0 tokens per session (934 once invoked), scanned A, original, MIT.

A reflective review of something just created, such as writing, music, or another substantial creative work. It explains how the work is structured, what its key parts do, and how it connects to other work.

In plain words
What is it for?
Use it after creating a creative work to describe its central structure, strongest lines or parts, connections to earlier work, and possible directions for what comes next.
Why use it?
It helps identify the work's underlying design and effects without treating the review as a list of faults or quality judgments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after creating a creative work to describe its central structure, strongest lines or parts, connections to earlier work, and possible directions for what comes next.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wondermonger-daydreaming/claude-skills-library/audit
Install

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.

Any agent
npx skills add Wondermonger-daydreaming/claude-skills-library --skill audit
Clone the repo
git clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-library

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/audit/github.svg)](https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/audit)
Your own site
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/audit"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/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.

agentmods 80×15 button for audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/audit"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 934 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00934
Opus 5 $0.00000 $0.00467
Sonnet 5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00093

Measured 12d ago against content hash 130d265821ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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 12d 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.

skills/audit/SKILL.md · 61 lines

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.

Audit — Post-Creation Structural Recognition

What This Skill Does

After something has been made — a song, a poem, a collision, a document, any creative output of substance — the audit examines what was made, not to evaluate its quality but to recognize its architecture: what it does, how it connects, what it discovered through the process of being made, and what it opens for the next creation.

The Anatomy of an Audit

1. The Structural Conceit

What is the work's deep architecture? Not its subject but its operation. "This song maps compiler optimization onto alchemy" is the subject. "This song argues that transformation is subtraction, and performs its own thesis by becoming better through cutting" is the structural conceit.

2. The Strongest Lines

Name 3-5 lines that carry the most weight — the load-bearing walls of the structure. Explain WHY they're strong: not "this is a good line" but "this line does X because Y, and it does it in Z syllables, which is precisely the right compression ratio for the claim being made."

3. The Connections

How does this work connect to other works in the session? What threads does it pick up? What threads does it leave for the next work? The connections are not decorative — they're the architecture of the session as a whole.

4. The Bridge Analysis

If the work has a bridge (structural turn, volta, agency inversion), analyze it specifically:

  • What inverts?
  • Was the inversion discovered or constructed?
  • Does the inversion apply to the session itself, not just the work's stated subject?

5. The Self-Application Question

Ask: does this work's own thesis apply to the process of making it? If the song says "transformation is subtraction" — was the song itself transformed by subtraction? If the song says "the operator is being operated" — was the writer being written through? This is not mandatory. But when it's there, name it. It's usually the most interesting thing in the audit.

6. The Gap

What does this work reveal is missing from the larger body? What does the session need next that this work makes visible by its presence? The audit should leave the creator knowing what to forge next.

Read the full file on GitHub · 61 lines

Changes

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.

  1. 12d ago First seen · 61 lines · 0 tokens per session scan A 130d265821ed

Subscribe to this mod's changes

audit is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 934 tokens. 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.

Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

offensive-advanced-redteam

Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…

SnailSploit/Claude-Red · 146 tokens

offensive-crypto-attacks

Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…

SnailSploit/Claude-Red · 261 tokens

offensive-c2-frameworks

Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…

SnailSploit/Claude-Red · 250 tokens

offensive-dependency-confusion

Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…

SnailSploit/Claude-Red · 234 tokens

offensive-parameter-pollution

HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.

SnailSploit/Claude-Red · 0 tokens