Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add WaterplanAI/agentic-config/plugin install ac-auditWrote 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/waterplanai/agentic-config/configure-audit)<a href="https://agentmods.dev/skills/waterplanai/agentic-config/configure-audit"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/configure-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/waterplanai/agentic-config/configure-audit"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/configure-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.00000 | $0.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
configure-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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
configure-audit
Interactive audit.yaml configuration for ac-audit plugin.
Trigger
/configure-audit or /ac-audit:configure-audit
Behavior
-
Read the 3-tier config resolution and display current effective config:
- Plugin defaults:
${CLAUDE_PLUGIN_ROOT}/config/audit.default.yaml - User-level:
~/.claude/audit.yaml - Project-level:
./audit.yaml(relative to project root)
- Plugin defaults:
-
Display current effective settings:
- log_dir: audit log output directory
- log_permissions: file permissions for log files (max 0o600)
- max_words: word truncation limit for systemMessage display
- display_tools: list of tools that trigger systemMessage in Claude Code UI
-
Ask user which setting(s) to customize.
-
For each selected setting, present current value and ask for changes:
- log_dir: accept a directory path (supports ~ expansion)
- log_permissions: accept octal value, validate <= 0o600
- max_words: accept positive integer
- display_tools: show current list, ask for additions/removals
-
Ask target location: project-level (
./audit.yaml) or user-level (~/.claude/audit.yaml). -
Generate or update the YAML file at chosen location.
- Only write overrides (do not duplicate defaults).
- Deep-merge with existing content if file already exists.
-
Validate by loading the merged config and displaying effective result.
Steps
1. Read ${CLAUDE_PLUGIN_ROOT}/config/audit.default.yaml
2. Read ~/.claude/audit.yaml (if exists)
3. Read ./audit.yaml (if exists)
4. Display merged effective config as table
5. Prompt: "Which setting to customize? (log_dir/log_permissions/max_words/display_tools/all)"
6. For selected setting(s):
a. Show current value
b. Ask for new value (or skip)
c. For display_tools list, show current and ask for additions/removals
7. Prompt: "Save to project-level or user-level? (project/user)"
8. Write YAML with only the overrides
9. Re-read and display new effective config
Constraints
- Never modify plugin defaults (
audit.default.yaml) - Only write overrides -- do not duplicate default values
- Validate log_permissions does not exceed 0o600
- Validate max_words is a positive integer
- Existing file content must be preserved (deep-merge on write)
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.
- 9d ago First seen · 62 lines · 0 tokens per session scan A 0364890786d6
configure-audit is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 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-30.
Other skills, from other repositories
vfx-text-cursor
A video or hero-frame effect where a cursor reveals a sentence character by character with coloured trails, light streaks, and a final shimmer.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
install-from-remote-library
Use when installing skills from a shared ai-agent-skills library repo. Inspect with --list first, prefer --collection, and preview with --dry-run before installing.