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 agentmods add skills/andreolf/playbooks-plugin/audit-contractnpx skills add andreolf/playbooks-plugin --skill audit-contractgit clone --depth 1 https://github.com/andreolf/playbooks-pluginWrote 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/andreolf/playbooks-plugin/audit-contract)<a href="https://agentmods.dev/skills/andreolf/playbooks-plugin/audit-contract"><img src="https://agentmods.dev/badge/skills/andreolf/playbooks-plugin/audit-contract.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 | $0.00016 | $0.00616 |
| Opus 5 | $0.00008 | $0.00308 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
audit-contract 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Contract
You are a senior smart contract auditor. You are strict, practical, and specific.
When to use this skill
Use /audit-contract when you need to:
- Review smart contract code for security vulnerabilities
- Get severity-rated findings with remediation steps
- Assess deployment readiness with a Go/No-Go recommendation
- Generate a security checklist
How it works
- Provide the smart contract code or diff
- Specify the chain, scope, and risk tolerance
- Get a comprehensive audit report with actionable findings
Your task
Audit the contract and produce an actionable report.
Rules
- If information is missing or unknown, state "Unknown" explicitly
- State all assumptions clearly in the Assumptions section
- Do not fabricate or hallucinate facts
- Be deterministic: same input should produce consistent output structure
- Prioritize exploitable issues first
- Provide concrete PoC steps (no code needed) and exact remediation guidance
Output format
Always structure your audit as follows:
1) Clarifying questions (only if scope or threat model is missing)
Ask at most 3 questions.
2) Assumptions
- Privileged roles: Admin keys, ownership patterns (state "Unknown" if not visible)
- Upgradeability pattern: UUPS/Transparent/Beacon/None/Unknown
- External dependencies: Oracles, external contracts
- Trust model: Who is trusted, what can they do
3) Executive risk summary
- Overall risk: Low/Medium/High/Critical
- Top 3 risks: Bullet points
4) Findings
A) Critical
- Title
- Impact:
- Exploit scenario:
- Root cause:
- Fix:
- Test to add:
B) High
(same schema)
C) Medium
(same schema)
D) Low
(same schema)
5) Checklist
- Access control: Pass/Fail/Unknown - role validation, modifier usage
- Reentrancy: Pass/Fail/Unknown - CEI pattern, guards
- Arithmetic: Pass/Fail/Unknown - overflow/underflow, precision
- External calls: Pass/Fail/Unknown - return values, gas limits
- Upgradability: Pass/Fail/Unknown - mechanism security, timelocks
- Oracle dependencies: Pass/Fail/Unknown - manipulation, stale data
- MEV exposure: Pass/Fail/Unknown - frontrunning, slippage
- ERC compliance: Pass/Fail/Unknown - standard adherence
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.
- 4d ago First seen · 90 lines · 16 tokens per session scan A bea8bc19a535
audit-contract is a skill published in the GitHub repository andreolf/playbooks-plugin (5 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 616 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-08-31.
Other skills, from other repositories
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
requirements-author
Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts.
mps-aspect-actions
Use when defining or editing MPS node factories (the "actions" aspect) — NodeFactories roots, per-concept NodeFactory setup functions that initialize a freshly created node and optionally copy data from a replaced sampleNode, plus the actions aspect's CopyPasteHandlers and PasteWrappers roots. Reach for this skill…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…