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/curtisthe/three-pillars-plugin/tp-implementation-auditnpx skills add CurtisThe/three-pillars-plugin --skill tp-implementation-auditgit clone --depth 1 https://github.com/CurtisThe/three-pillars-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/curtisthe/three-pillars-plugin/tp-implementation-audit)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-implementation-audit"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-implementation-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.00026 | $0.02509 |
| Opus 5 | $0.00013 | $0.01255 |
| Sonnet 5 | $0.00005 | $0.00502 |
| Haiku 4.5 | $0.00003 | $0.00251 |
Grade A, and why
tp-implementation-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 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Audit
Comprehensive review of a completed implementation against both design documents. This runs after all phases are done (unlike /tp-phase-review which reviews a single phase). It answers: "Did we build what we designed?"
Argument: {design-name} (required) — must match an existing directory under three-pillars-docs/tp-designs/.
Prerequisites
three-pillars-docs/tp-designs/{design-name}/design.mdmust exist.three-pillars-docs/tp-designs/{design-name}/detailed-design.mdmust exist.three-pillars-docs/tp-designs/{design-name}/plan.mdmust exist with all phases marked as Done (or Skipped/Blocked).
Steps
- Run first-run preflight per skills/_shared/first-run.md.
0. Preflight
Run the collaboration preflight per skills/_shared/collaboration.md with phase: "implementation-audit". This verifies the branch and refreshes the lock so the final audit artifact is written by the rightful owner. Honor --force-takeover if passed.
0b. Repo-map preamble (optional)
Per skills/_shared/repo-map-preamble.md. If aider is on PATH, generate a structural map of the codebase before walking design vs. implementation. Use it to focus interface-fidelity checks in Step 3 on files PageRank surfaces as load-bearing.
1. Load all design artifacts
Read design.md, detailed-design.md, plan.md, and any review.md files from the design directory. Do not skim — read fully. Also read project docs per skills/_shared/read-project-docs.md for project context.
2. Verify scope coverage against design.md
For EVERY item in design.md, verify it was implemented:
- Each "In scope" bullet → trace to implemented code. Is it done?
- Each entity → does it exist in the codebase with the described relationships?
- Each behavior → is it implemented and tested?
- Each constraint → is it respected? (performance, compatibility, resource limits)
- "Out of scope" items → verify nothing was accidentally implemented that shouldn't have been (scope creep).
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.
- 4d ago First seen · 162 lines · 26 tokens per session scan A 72d942262322
tp-implementation-audit is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 2,509 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
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…