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-docs-initnpx skills add CurtisThe/three-pillars-plugin --skill tp-docs-initgit clone --depth 1 https://github.com/CurtisThe/three-pillars-pluginWhat 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.00070 | $0.01810 |
| Opus 5 | $0.00035 | $0.00905 |
| Sonnet 5 | $0.00014 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
tp-docs-init 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Init
Analyze the current codebase and scaffold the three project docs that the TDD pipeline uses for context (alongside three-pillars-docs/vision.md, which is created by /tp-setup).
No arguments — operates on the current repository.
Prerequisite
three-pillars-docs/vision.md should exist — it's the "why" pillar that the roadmap, architecture, and known-issues docs frame themselves against. If it's missing, tell the user and recommend running /tp-setup first. Do not block: the user can opt to proceed without a vision, but the resulting scaffolds will be weaker because there's no "why" to anchor current state and priorities against.
Environment prereq — optional status line
While you're scaffolding docs, also check whether the plugin's optional status line is installed. The plugin ships a statusline.sh script that shows context-window usage, active design, and git status — but it requires a one-time copy to ~/.claude/statusline.sh to activate (the plugin's settings.json already references that path).
Check:
test -x "$HOME/.claude/statusline.sh" && echo "installed" || echo "missing"
If missing, do not block the docs scaffolding. After the docs are written, surface a one-line recommendation to the user:
Optional: the three-pillars status line is not installed. Run
cp statusline.sh ~/.claude/statusline.sh && chmod +x ~/.claude/statusline.shfrom the plugin's install directory to enable the context-window progress bar. Skip this if you don't want a custom status line — nothing breaks either way.
If installed, say nothing (it's already working).
This check lives here, in docs-init, because /tp-docs-init is where a user first encounters the architecture of a fresh project — it's the natural moment to surface environment setup the user may have skipped during install. It is NOT a hard prerequisite: proceed with the scaffolding regardless of the statusline's state.
Steps
- Run first-run preflight per skills/_shared/first-run.md.
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.
- 3d ago First seen · 93 lines · 70 tokens per session scan A 0a37725f68e5
tp-docs-init is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,810 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.
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…