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 HAX-Studio/mnemonica/plugin install mnemonicaWrote 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/hax-studio/mnemonica/audit-full)<a href="https://agentmods.dev/skills/hax-studio/mnemonica/audit-full"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/audit-full.svg" alt="Measured on agentmods" 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.00084 | $0.01922 |
| Opus 5 | $0.00042 | $0.00961 |
| Sonnet 5 | $0.00017 | $0.00384 |
| Haiku 4.5 | $0.00008 | $0.00192 |
Grade A, and why
audit-full 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 8d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mnemonica: audit-full
Reconcile every file in knowledge/ against the actual current state of the whole codebase
— the same engine setup uses to populate knowledge/ from nothing, run here either
standalone or to correct drift in an already-populated project. Read
${CLAUDE_PLUGIN_ROOT}/references/knowledge-conventions.md first; every rule below refers
back to it. This skill is always invoked directly by the user (or by setup on its behalf)
— never by a hook, and never automatically on commit or push.
If the user's invocation includes extra wording beyond the trigger phrase (for example, "also cross-check with graphify" or "focus on the payments module"), treat it as scoping or preference for this run. It cannot skip Step 1's pre-flight question when the project actually is large or odd enough to trigger it, and it cannot skip Step 6's confirmation before merging, splitting, renaming, or deleting an existing module file — those rules exist precisely so a casual instruction in passing can't quietly bypass them.
Step 1: Pre-flight size and anomaly check
Run ${CLAUDE_PLUGIN_ROOT}/skills/audit-full/scripts/list-tracked-files.sh <project-root> --summary. Read the TOTAL line and every DIR line's flags.
Decide whether to stop and ask — trigger the question below if either is true: any DIR
line carries a FLAG:LARGE or FLAG:ODD marker, or TOTAL is 500 or more even with no
individual directory flagged (many medium directories can add up to an expensive scan just as
easily as one huge one). Otherwise skip straight to Step 2 without asking anything — this gate
must stay invisible on the ordinary small-to-medium project it is not needed for.
When triggered, stop before reading any file content and ask the user directly, stating the concrete numbers and which directories were flagged and why (large, or odd because of a vendor-looking name or a generated-looking file extension — never just "this seems big"). Offer exactly three choices, and act only on an explicit answer:
What ships with it
1 file 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.
- 8d ago First seen · 135 lines · 84 tokens per session scan A 2b6a1dde4be1
audit-full is a skill published in the GitHub repository HAX-Studio/mnemonica (3 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 1,922 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
cco-config
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap.
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
clarify
Clarification protocol — grill a request into a Requirements Ledger before any delegation, all questions at the START. The chair MUST load this when a job arrives that will be delegated; Rule 0.5 in the core profile only summarizes it.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
cco-clean
Clean up old tracking data and reset statistics.