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-promotegit 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-promote)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-promote"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-promote.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.1 | $0.00084 | $0.02606 |
| Opus 5 | $0.00042 | $0.01303 |
| Sonnet 5 | $0.00017 | $0.00521 |
| Haiku 4.5 | $0.00008 | $0.00261 |
Grade A, and why
tp-promote 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 6d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tp-promote <slug>
Turn a rich seed.md into a committed, floor-clearing design.md on the
tp/<slug> branch — the cold-start pre-step before a design-ready fleet pass.
Exactly one human touch: a single batched confirm block derived from the
seed's ## Open questions. After the operator answers, this skill drafts
design.md, validates the floor, commits, and tells the operator to run
/tp-run-full-design <slug> --skip-design.
No --auto mode — the one batched confirm is the deliberate human gate.
Arguments
{slug}(required) — kebab-case design name matching[a-z0-9-]+, validated perskills/_shared/validate-name.md. Must match an existing directory underthree-pillars-docs/tp-designs/{slug}/that contains aseed.md.--force-takeover(optional) — claim the lock even when another developer holds it. The prior holder is recorded inprevious_owners[].
Steps
-
Run first-run preflight per
skills/_shared/first-run.md. -
Validate
<slug>perskills/_shared/validate-name.md. Reject any value containing/,.., spaces, or characters outside[a-z0-9-]. After validation, track the design in.claude/last-design(MRU update). -
Collaboration preflight per
skills/_shared/collaboration.md:- If on
master/main, offer to create/switch totp/<slug>. - Read
three-pillars-docs/tp-designs/<slug>/lock.json. Ifowneris another developer and--force-takeoverwas NOT passed, refuse and surface the holder. If--force-takeoverwas passed, record the prior owner inprevious_owners[]and claim the lock. Setphase: "promote". - Write
lock.jsonback to disk (do NOT commit yet — lock commits withdesign.mdin Step 8).
- If on
-
Require
seed.md: check thatthree-pillars-docs/tp-designs/<slug>/seed.mdexists and is non-empty. If absent, stop:seed.mdnot found for<slug>. Authorthree-pillars-docs/tp-designs/<slug>/seed.md(a rich seed with a## Open questionssection) before promoting.
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.
- 6d ago First seen · 209 lines · 84 tokens per session scan A 99d13265692a
tp-promote is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 2,606 once invoked, about $0.0004 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…
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…
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…