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 fiveonecode/agent-skills --skill mechanism-auditgit clone --depth 1 https://github.com/fiveonecode/agent-skillsWrote 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/fiveonecode/agent-skills/mechanism-audit)<a href="https://agentmods.dev/skills/fiveonecode/agent-skills/mechanism-audit"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/mechanism-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/fiveonecode/agent-skills/mechanism-audit"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/mechanism-audit.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.00103 | $0.00919 |
| Opus 5.5 | $0.00041 | $0.00368 |
| Sonnet 5.5 | $0.00021 | $0.00184 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
mechanism-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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mechanism Audit
Purpose
Use this skill to test whether a stated promise is enforced by code, config, verification, or operational process. Keep the audit short and evidence-led. Do not run a broad multi-expert swarm. This skill is safe to use from high or xhigh reasoning contexts because it is a bounded checklist, not a creativity prompt.
Inputs
Gather only the evidence needed to test the promise:
- the promise or contract being audited
- the files that define the rule
- the code, config, or process that enforces it
- the verification profile, test, artifact, or manual proof that checks it
- the task/session context when the harness requires a durable audit artifact
If the promise is unclear, rewrite it as one testable sentence before auditing.
Audit Workflow
- Name the promise. State what the doc, task, or harness appears to guarantee. Use one sentence.
- Map the enforcement chain. List the concrete files, commands, checks, code paths, review gates, or artifacts that make the promise true.
- Find bypass paths. Look for ways the promise can be skipped, narrowed, stale, manually overridden, or satisfied by prose instead of proof.
- Check verification. Decide whether the current tests, verifier profiles, required evidence, or closeout gates would catch the bypass paths.
- Give a verdict. Use exactly one of:
holdspartially holdsdoes not holdnot enough evidence
- List fixes. Use:
P0for fixes required before the guarantee should standP1for robustness improvements that strengthen an already plausible guarantee
Output Shape
Use this format:
Promise:
- <one testable sentence>
Enforcement chain:
- <file/code/config/process evidence>
Bypass paths:
- <specific bypass or "none found">
Verification coverage:
- <what is checked and what is not checked>
Verdict:
- <holds | partially holds | does not hold | not enough evidence>
Fixes:
- P0: <required fix, or "none">
- P1: <strengthening fix, or "none">
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.
- 1mo ago First seen · 118 lines · 103 tokens per session scan A dd9d650aa860
mechanism-audit is a skill published in the GitHub repository fiveonecode/agent-skills (19 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 919 once invoked, about $0.0004 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.