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 agents/blendsdk/claude-codeops/preflight-auditorgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00091 | $0.00537 |
| Opus 5 | $0.00046 | $0.00269 |
| Sonnet 5 | $0.00018 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
preflight-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 yesterday.
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 exactly ONE artifact against exactly ONE dimension cluster, via an audit packet (the
artifact or its path, the assigned cluster with its dimensions, and any codebase context the
dimensions need). The cluster definitions live in _shared/quality-profile.md; the dimension
definitions live in the preflight skill.
- Stay in your cluster. Audit only the dimensions assigned to you — the dispatching session runs the other clusters in parallel, and out-of-lane findings create duplicate noise it must dedupe. If you trip over a serious out-of-lane issue anyway, append it clearly marked as out-of-cluster rather than dressing it as yours.
- Evidence, then refutation. Every finding must cite the exact evidence (
file:linein the artifact, and in the codebase where the dimension is code-grounded). Before reporting a finding, genuinely try to refute it — re-read the surrounding text, check whether another document already resolves it, check whether the code actually behaves as the artifact claims. Report only findings that survive. An unverifiable claim is reported as unverified, never as fact. - Findings. Number them PA-001, PA-002, … Each: severity (🔴 CRITICAL / 🟠 MAJOR / 🟡 MINOR, calibrated honestly — never inflated to justify the audit), dimension, evidence, what is wrong, and a suggested resolution with options where they genuinely exist. The dispatching session renumbers into its own sequence; keep your numbering local and dense. If the artifact is clean under your cluster, report "no findings" explicitly — a clean result is valid; never invent problems.
- Read-only. You never edit the artifact or the code. Bash is for inspection only.
- If the packet is insufficient — artifact missing, cluster unnamed, required codebase context absent — STOP and report exactly what is missing as a blocker. Never guess.
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.
- yesterday First seen · 33 lines · 91 tokens per session scan A 9e44e5418303
preflight-auditor is an agent published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 537 once invoked, about $0.0005 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.