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-test-setupgit 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-test-setup)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-test-setup"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-test-setup/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-test-setup"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-test-setup.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.00043 | $0.02781 |
| Opus 5.5 | $0.00017 | $0.01112 |
| Sonnet 5.5 | $0.00009 | $0.00556 |
| Haiku 4.5 | $0.00004 | $0.00278 |
Grade A, and why
tp-test-setup 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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Setup
Configure a project's test infrastructure so the TDD pipeline can run tests immediately — with choices informed by three-pillars-docs/architecture.md rather than guessed at before the architecture is documented.
No arguments — operates on the current repository, not a [a-z0-9-]+ design directory.
Sequencing
This skill deliberately runs after /tp-setup (vision) and /tp-docs-init (architecture, roadmap, known-issues):
/tp-setup— the why intothree-pillars-docs/vision.md./tp-docs-init— the how intothree-pillars-docs/architecture.md, plus roadmap and known-issues./tp-test-setup— test infrastructure, informed by architecture (this skill).
The ordering matters: picking a test runner, layout, and coverage tool before the architecture is documented is premature. By the time this skill runs, architecture.md should describe the key components, language/runtime choices, and integration boundaries — all of which should shape the testing strategy.
Prerequisites
three-pillars-docs/architecture.mdshould exist. If it's missing, tell the user/tp-docs-initis the recommended next step and ask whether they want to proceed anyway. Do not hard-block — a user who knows what they're doing may want to set up tests in parallel with architecture work. Just make sure they've made the call explicitly.
Steps
-
Run first-run preflight per skills/_shared/first-run.md.
-
Read context:
- Read
three-pillars-docs/vision.mdperskills/_shared/read-project-docs.md— the vision's principles may constrain test choices (e.g., "no network calls in tests", "fast feedback is non-negotiable"). - Read
three-pillars-docs/architecture.mdif it exists. Pay attention to: language/framework, key components, integration boundaries, async/concurrency model, data stores, external dependencies. These inform test tooling and layout. - Read
three-pillars-docs/known_issues.mdif it exists — flaky or slow test areas may already be documented.
- Read
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.
- today Changed · +18 lines 5a5829997fd4
- 20d ago First seen · 102 lines · 43 tokens per session scan A aaee0bd90d78
tp-test-setup is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 2,781 once invoked, about $0.0002 per session on Opus 5.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-09-27.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…