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 skills add CurtisThe/three-pillars-plugin --skill tp-design-detailgit 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-design-detail)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-design-detail"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-design-detail/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/curtisthe/three-pillars-plugin/tp-design-detail"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-design-detail.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.00031 | $0.01407 |
| Opus 5 | $0.00015 | $0.00704 |
| Sonnet 5 | $0.00006 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
tp-design-detail 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Low-Level Detailed Design
Turn a high-level design into a concrete implementation blueprint.
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. If not, tell the user to run/tp-design {design-name}first and stop.
Steps
-
Run first-run preflight per skills/_shared/first-run.md.
-
Run collaboration preflight per
skills/_shared/collaboration.mdwithphase: "detail". This verifies the branch and refreshes the lock for this design. Honor--force-takeoverif passed. 1b. Repo-map preamble (optional) perskills/_shared/repo-map-preamble.md. Ifaideris on PATH, generate a structural map of the codebase before exploration. The map informs which files are load-bearing per PageRank — use it to focus the Explore agent / Grep / Glob calls in step 3 instead of scanning blind. -
Read
design.mdfrom the design directory. -
Explore the codebase to understand existing patterns, conventions, and integration points. Use the Explore agent or Grep/Glob as needed. Understand where the new code will live and what it will touch.
-
Read project docs per
skills/_shared/read-project-docs.md. -
Have a conversation with the user to resolve any open questions from design.md and make key implementation decisions:
- Where does this code live? New files, existing files, new module?
- What are the public interfaces? (function signatures, class APIs, config schema)
- What are the test boundaries? (what gets unit-tested, what's integration, what's mocked)
- What are the dependencies? (existing modules to import, new packages needed)
- What's the processing model? (sync/async, batched, streaming, event-driven)
-
Write
three-pillars-docs/tp-designs/{design-name}/detailed-design.mdwith this structure. If design.md carries aweight-classfrontmatter block, stamp the same class onto this artifact (python3 -c "import sys; sys.path.insert(0,'skills/_shared'); from weight_class import write_class; write_class('<artifact>', '<class>')"or write the---\nweight-class: <class>\n---block directly at the top):
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.
- 9d ago First seen · 97 lines · 31 tokens per session scan A b37c1ca2138b
tp-design-detail is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,407 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-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…