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-mergegit 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-merge)<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-merge"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-merge.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.00096 | $0.02741 |
| Opus 5 | $0.00048 | $0.01371 |
| Sonnet 5 | $0.00019 | $0.00548 |
| Haiku 4.5 | $0.00010 | $0.00274 |
Grade A, and why
tp-merge 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tp-merge — the land gate (irreversible gh pr merge)
/tp-merge is the land skill: it crosses the one irreversible boundary in the
framework — running gh pr merge to land a reviewed PR onto its base. It is the sole
code site where the "the framework never crosses the irreversible boundary without an
explicit, current human approval" guarantee is enforced in code.
It does not sync the base into the branch, resolve living-doc conflicts, or rewrite
tracked files — that reversible base-into-branch operation is the separate
/tp-merge-from-main skill. /tp-merge only gates and lands.
Two distinct skills, one former name. Before the human-approval-merge-gate design (D7),
/tp-mergewas the base-sync conflict resolver. That half is now/tp-merge-from-main. The/tp-mergename is retained for this land half, because operator and orchestrator references to "/tp-merge" mean land/merge. Keep them distinct:/tp-merge-from-mainsyncs the base in (reversible, below the gate);/tp-mergelands the PR out (irreversible, behind the gate).
Arguments
{pr-url|design-name}(required) — the PR to land. A PR URL is used directly; a design name resolves to its open completion PR.
Prerequisites
ghCLI installed and authenticated (the merge runsgh pr merge).- The PR has been reviewed and is reviewed-stable (the autonomous loop pauses here — this step is the human's).
The gate (load-bearing)
The land is gated by require_merge_gate_pass(pr_url) from
skills/tp-merge-from-main/scripts/merge_gate.py — the fail-closed enforcing form of
the deterministic merge gate. It evaluates the gate's predicates over the PR head SHA and
raises MergeGateBlocked on any non-PASS verdict, so a caller that ignores the return
value still cannot proceed. The gate now carries seven head-SHA-keyed predicates:
- threads_resolved — all review threads resolved. When this predicate blocks
the refusal,
land.pyprints a remediation pointer:/tp-pr-iterate {design} --dispose-only(reply-and-resolve out-of-band). - mergeable — PR is in MERGEABLE state.
- checks_success — all required CI checks settled and concluded SUCCESS.
- copilot_on_head — Copilot has reviewed the current head SHA.
- human_approved — a current APPROVED human review from a non-automation human
is present on the head SHA. Absent / stale (review predates the head) /
automation-authored → INDETERMINATE. This is the predicate the autonomous path can never
satisfy: the autonomous path cannot produce a non-automation APPROVED review on the
head out-of-band. The review's immutable
commit_idis the currency check — a real content push leaves the prior review pointing to the old head (non-current → fail-closed). - ci_local_stamp — a fresh SHA-keyed local-CI green stamp (written by
scripts/ci-local.shafter all checks pass). Absent, stale, or dirty → FAIL; runscripts/ci-local.shto satisfy this predicate.scripts/ci-local.shis a dev-repo file the plugin never installs — a consumer repo has no documented way to produce this stamp. Opt out per-repo viareview.require_ci_local_stamp: false. - review_proof_on_head — a head-bound, non-degraded proof-of-review digest comment
exists on the current head SHA, authored by a trusted automation identity: the
framework's own gh login + config
review.automation_identitiesextras, and NOTHING else — the Copilot/native-bot automation floor is deliberately not digest-trusted (those identities never legitimately post digests, and a prompt-injected Copilot comment must not mint proof), and a drive-by commenter pasting a matching digest does NOT count. The/tp-pr-iteratereview arm posts it each round. Absent / stale (head moved) / degraded / untrusted-author → INDETERMINATE; re-run the proof-bearing review on the current head. Opt out per-repo viareview.require_review_proof: false.
What ships with it
5 files 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.
- 7d ago First seen · 160 lines · 96 tokens per session scan A c2c8418b942d
tp-merge is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 2,741 once invoked, about $0.0005 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.