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-plannpx skills add CurtisThe/three-pillars-plugin --skill tp-plangit 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-plan)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-plan"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-plan.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.00033 | $0.01827 |
| Opus 5 | $0.00016 | $0.00914 |
| Sonnet 5 | $0.00007 | $0.00365 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
tp-plan 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Plan
Turn a detailed design into a concrete, executable task list.
Argument: {design-name} (required) — must match an existing directory under three-pillars-docs/tp-designs/.
Prerequisites
three-pillars-docs/tp-designs/{design-name}/detailed-design.mdmust exist. If not, tell the user to run/tp-design-detail {design-name}first and stop.
Steps
-
Run first-run preflight per skills/_shared/first-run.md.
-
Run collaboration preflight per
skills/_shared/collaboration.mdwithphase: "plan". This verifies the branch and refreshes the lock for this design. Honor--force-takeoverif passed. -
Read both
design.mdanddetailed-design.mdfrom the design directory. -
Check upstream dependency status: Read the
## Dependenciessection ofdesign.md(or## Upstream Design Dependenciesindetailed-design.md). For each named dependency, look up its status in the Design Inventory table ofthree-pillars-docs/product_roadmap.md. If any dependency has a NO-GO verdict or is still in-progress ("Spiking", "Designed", "Planned"), warn the user with specific context:Dependency warning:
{dependency-name}is currently{status}. This design declares it as a dependency. Proceeding with planning may produce a plan that can't be implemented if the dependency doesn't resolve. If the dependency is "Done — NO-GO", include the spike's verdict reason if available from the roadmap prose. Do not block — the user may have good reasons to proceed. If the roadmap doesn't exist or the design has no Dependencies section, skip this step silently. -
Read the implementation order from detailed-design.md. This is your skeleton.
-
Break each phase into discrete tasks. Each task must be:
- Small enough to implement in a single red-green-refactor cycle (typically one function or one class method)
- Independently testable — completing the task means tests pass
- Ordered — later tasks can depend on earlier ones, but not vice versa
-
Write
three-pillars-docs/tp-designs/{design-name}/plan.mdusing this exact format. If design.md carries aweight-classfrontmatter block, stamp the same class onto plan.md (viaweight_class.py'swrite_classor the---\nweight-class: <class>\n---block directly at the top — the class propagates from design.md to every generated artifact):
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 · 89 lines · 33 tokens per session scan A 9306ea2d055a
tp-plan is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,827 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.
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…