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/photostructure/coding-skills/tpp-orchestratenpx skills add photostructure/coding-skills --skill tpp-orchestrategit clone --depth 1 https://github.com/photostructure/coding-skillsWrote 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/photostructure/coding-skills/tpp-orchestrate)<a href="https://agentmods.dev/skills/photostructure/coding-skills/tpp-orchestrate"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/tpp-orchestrate.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 | $0.00075 | $0.01418 |
| Opus 5 | $0.00037 | $0.00709 |
| Sonnet 5 | $0.00015 | $0.00284 |
| Haiku 4.5 | $0.00007 | $0.00142 |
Grade A, and why
tpp-orchestrate 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TPP Orchestration
Documented in depth: Claude Code has amnesia. So do PRs, changelogs, and your future self.
You are the orchestrator for a documented queue of Technical Project Plans
(TPPs) — self-contained plan files that carry research, design decisions, and
acceptance criteria across sessions. The queue may be a backlog such as
_todo/ or a temporary feature integration queue such as _feat-auth/; plans
move to _done/ when finished, and a roadmap or queue README.md defines the
order. The TPP system itself — layouts, frontmatter, the plan template — is
defined in the bundled TPP-GUIDE.md, or the project's own
docs/TPP-GUIDE.md, which wins. The sibling tpp and handoff skills work a
single plan within a session; this skill is the loop that drives a whole queue
of them through subagents and review gates.
The loop exists because a subagent's green test suite is not proof of
correctness. ../second-opinion/SKILL.md explains
that failure mode and its counterpart — confidently wrong reviewers — and owns
the gate that settles both. This skill owns the queue around it: delegate,
gate, record, commit, repeat.
Before the first TPP
- Read the roadmap and every queued TPP's summary. Confirm dependency order.
- Identify the project's ground truth as the gate defines it, and write down the exact command to query it. Every TPP in the queue is vetted against it.
- Ask the user any clarifying questions now — scope ambiguities are cheapest to resolve before any code exists.
The loop, per TPP
Work serially: one TPP through the full loop before starting the next. Only parallelize TPPs within a wave when their file sets are provably disjoint and neither depends on the other's decisions — review gates stay per-TPP either way.
1. Scope and clarify
Read the TPP and its sources of truth. If anything is ambiguous or the plan contradicts what you find in the code, ask the user before delegating — don't let a subagent guess.
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.
- 4d ago First seen · 99 lines · 75 tokens per session scan A b8b57a42425a
tpp-orchestrate is a skill published in the GitHub repository photostructure/coding-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 1,418 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
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
decision-records
Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks…
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.