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-spike-autogit 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-spike-auto)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-spike-auto"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-spike-auto.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.00030 | $0.01834 |
| Opus 5 | $0.00015 | $0.00917 |
| Sonnet 5 | $0.00006 | $0.00367 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
tp-spike-auto 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 7d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Spike Pipeline
Two-phase spike: interactive design conversation, then autonomous execution of the full pipeline. Produces a decision log for human review.
Arguments:
{spike-name}(required) — kebab-case name, becomes the directory underthree-pillars-docs/tp-designs/.--parent {design-name}(optional) — links this spike to a parent design.
Phase 1: Interactive Design (same as /tp-spike)
-
Run first-run preflight per skills/_shared/first-run.md.
-
Validate
{spike-name}: must match[a-z0-9-]+. -
Resolve the design directory:
three-pillars-docs/tp-designs/{spike-name}/. Create if needed. -
Run collaboration preflight per
skills/_shared/collaboration.mdwithphase: "design". This is interactive (Phase 1), so prompt the user for branch creation or takeover as described in the shared doc. Honor--force-takeoverif passed. Phase 2 will refresh the same lock through each delegated skill. -
Check for existing
design.md. If exists, ask the user whether to revise or start fresh. -
If
--parentis given, verify parent design exists and read it. -
Have a spike conversation. Draw out through questions:
- Hypothesis — what do we believe and want to validate?
- Success criteria — what does GO / PARTIAL / NO-GO look like?
- Experiments — what will we try, what do we expect to observe?
- Expected demos — what artifacts prove findings?
- Constraints — time budget, resource limits, dependencies.
- Parent linkage — if parent exists, what questions does this spike answer?
-
Write
design.mdusing the standard spike design format (see/tp-spikefor template). -
Ask the user: "Design complete. Ready to go autonomous? Once you confirm, I'll run plan → audit → implement → results without stopping. You can review decisions.md in the morning."
- If the user says no or wants changes, iterate on the design.
- If the user confirms, proceed to Phase 2.
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.
- 7d ago First seen · 128 lines · 30 tokens per session scan A dd095f783a21
tp-spike-auto is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,834 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…