Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPnpx agentmods add skills/eilodon/dps-superskills-mcp/audit-designWrote 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/eilodon/dps-superskills-mcp/audit-design)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/audit-design"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/audit-design/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/eilodon/dps-superskills-mcp/audit-design"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/audit-design.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.02721 |
| Opus 5 | $0.00028 | $0.01360 |
| Sonnet 5 | $0.00011 | $0.00544 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
audit-design 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 10d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit-Design — Pre-Implementation Risk Audit
Runs a compressed VHEATM FAST audit on the spec document produced by brainstorming.
Purpose: find domain risks, failure modes, and blind spots in the design before
a single line of code is written. Cheap to fix now. Expensive after implementation.
Announce: "I'm using audit-design to run a pre-implementation risk audit."
Trigger Conditions
This skill activates when either condition is true:
Condition A — Normal flow: spec frontmatter contains SPEC_APPROVED: true
(set by brainstorming after user approves the design document)
Condition B — Escalation flow: spec frontmatter contains SPEC_ESCALATION: true
(set by specialist-review when a CRITICAL/HIGH finding traces back to a spec-level decision)
In escalation flow, read the ESCALATION_FINDING field in the spec before running the audit —
it provides the specific finding that triggered re-review.
Idempotency Check
Before running, check if a risk assessment already exists:
grep -c "## Risk Assessment (audit-design)" docs/superskills/specs/<spec-file>.md
- Count = 0 → run full audit, append new section.
- Count ≥ 1 AND normal flow → check timestamp. If spec was modified after last audit → re-run with
UPDATElabel. If unchanged → skip, log "audit current". - Count ≥ 1 AND escalation flow → always re-run, append as
## Risk Assessment — Escalation (audit-design)with escalation finding as context. This is a new section, not an overwrite.
DPS Detection
# Check if DPS is present and status:
DPS_STATUS=$(grep "DPS STATUS:" .dps/spec/BLUEPRINT.md 2>/dev/null | head -1 | awk '{print $NF}')
echo "DPS STATUS: ${DPS_STATUS:-NOT_PRESENT}"
IF DPS_STATUS = DRAFT or PROOF-READY: → Run DPS-Aware Audit (Section below) IN ADDITION TO standard VHEATM FAST IF DPS_STATUS = NOT_PRESENT: → Run standard VHEATM FAST only (unchanged behavior) IF DPS_STATUS = APPROVED-SSOT or higher: → Idempotency check applies (re-audit only on escalation)
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.
- 10d ago First seen · 285 lines · 55 tokens per session scan A 4034a16bd05e
audit-design is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,721 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…