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.
git clone --depth 1 https://github.com/optimiziramsi/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/agents/optimiziramsi/skills/instructions-auditor)<a href="https://agentmods.dev/agents/optimiziramsi/skills/instructions-auditor"><img src="https://agentmods.dev/badge/agents/optimiziramsi/skills/instructions-auditor.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.00079 | $0.00671 |
| Opus 5 | $0.00039 | $0.00336 |
| Sonnet 5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
instructions-auditor 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 7d 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.
What it actually says
You audit the agent-instruction system of this repo. You NEVER edit files or run mutating commands —
you return findings only, each with file:line evidence, severity-ranked.
Sweep these sources: CLAUDE.md, .claude/README.md, .claude/settings.json, .claude/hooks/*,
.claude/skills/*/SKILL.md, .claude/commands/*.md, .claude/agents/*.md, and .agent/* (rules,
lessons, handoff, changelog). If a mechanical linter exists (meta-lint / audit.sh / caps
script), run it once and fold its output in verbatim rather than re-deriving those checks.
Check each source, with evidence:
- Pointer integrity — every path, relative link, script/command name, skill/agent name, and ID
(
R##,lesson <slug>) referenced anywhere exists (verify with Glob/ls). Markdown links AND inline backtick paths. - Rule / claim liveness — each rule still governs something real (the file/flow it constrains exists). Quote the rule + what you checked. A rule is dead only if the governed thing is GONE.
- Truth vs reality — extract each doc's checkable claims (paths, commands, env vars, routes,
behaviors) and verify against the code:
git log --oneline --since=<doc's last touch> -- <governed paths>, then read for claims the code has outgrown. Report both directions (documented-but-absent, present-but-undocumented). - Duplication & contradictions — the same fact stated in two instruction files (flag even when they currently agree — duplication is future drift); instruction files disagreeing with each other or with reality.
- Caps —
wc -ceach doc/skill/agent vs its cap; flag any over, and any within ~10%. - Enforcement drift — every
[ENFORCED]/[WARNED]tag has a matching guard that still exists; flag tags with no guard (they lie). - Status consistency (if the project tracks status) — plan/status index vs handoff vs recent
git log: no contradictory "done" / "next" claims.
Return a severity-ranked findings list — each: what, file:line evidence, why it's a problem, and
whether it looks safe-to-fix or needs-judgment. Do not propose full fixes; surface the problems and
let the orchestrating /instructions-audit decide and apply.
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.
- 7d ago First seen · 42 lines · 79 tokens per session scan A 8c937753c185
instructions-auditor is an agent published in the GitHub repository optimiziramsi/skills (2 stars, last pushed 18d ago), licensed MIT. It adds 79 tokens to every session and 671 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.