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/prebid/salesagent/auditnpx skills add prebid/salesagent --skill auditgit clone --depth 1 https://github.com/prebid/salesagentWrote 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/prebid/salesagent/audit)<a href="https://agentmods.dev/skills/prebid/salesagent/audit"><img src="https://agentmods.dev/badge/skills/prebid/salesagent/audit.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.00048 | $0.00776 |
| Opus 5 | $0.00024 | $0.00388 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Audit
Repeatable code review workflow for auditing migration changes. Produces structured review documents and beads issues for every finding.
Args
/audit [audit-target]
The audit target (optional, defaults to "full"):
- Branch:
KonstantinMirin/adcp-v3-upgrade— review all changes on branch - Commit range:
main..HEAD— review commits in range - "full": Audit entire codebase against architecture principles
What It Produces
- Change inventory by architectural layer (schema, business, boundary, transport, adapter, database, test)
- Layer-specific reviews against #1050/#1066 checklists
- Consolidated report in
docs/code-reviews/ - Beads issues for every finding not already tracked
Protocol
Step 1: Cook the molecule
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/migration-audit.yaml \
--var "AUDIT_TARGET={all_args}" \
--epic-title "Audit: {all_args}"
If no target specified, use "full":
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/migration-audit.yaml \
--var "AUDIT_TARGET=full" \
--epic-title "Audit: full codebase"
Dry run first (recommended):
python3 .claude/scripts/cook_formula.py \
--formula .claude/formulas/migration-audit.yaml \
--var "AUDIT_TARGET={all_args}" \
--epic-title "Audit: {all_args}" \
--dry-run
Step 2: Walk the molecule
bd ready → bd show <atom-id> → execute → bd close <atom-id> → repeat
Linear pipeline: inventory-changes → review-per-layer → consolidate → file-issues → commit-report.
Step 3: Done when report committed
Audit report in docs/code-reviews/, beads issues filed for all findings.
Layer Review Checklists
Each layer has a specific checklist (see formula for full details):
| Layer | Key Checks |
|---|---|
| Schema | Correct base class, no field duplication, exclude=True on internals |
| Business | No ToolError, no transport imports, ResolvedIdentity, no error dicts |
| Boundary | All _impl params exposed, version compat at boundary only |
| Transport | Shared _impl pattern, no business logic duplication |
| Database | SQLAlchemy 2.0, JSONType, correct column types |
| Adapter | No protocol code, proper error propagation |
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.
- 2d ago First seen · 103 lines · 48 tokens per session scan A 99855101867e
audit is a skill published in the GitHub repository prebid/salesagent (36 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 776 once invoked, about $0.0002 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…