Borrowing it
Nothing to install: this file belongs to tsz-org/tsz. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tsz-org/tsz/main/.agents/skills/tsz-pr-coordination/SKILL.mdgit clone --depth 1 https://github.com/tsz-org/tszWrote 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/tsz-org/tsz/tsz-pr-coordination)<a href="https://agentmods.dev/skills/tsz-org/tsz/tsz-pr-coordination"><img src="https://agentmods.dev/badge/skills/tsz-org/tsz/tsz-pr-coordination/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/tsz-org/tsz/tsz-pr-coordination"><img src="https://agentmods.dev/badge/skills/tsz-org/tsz/tsz-pr-coordination.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.00065 | $0.00591 |
| Opus 5.5 | $0.00026 | $0.00236 |
| Sonnet 5.5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
tsz-pr-coordination 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 23d 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.
What it actually says
TSZ PR Coordination
Use for PR body/state/review coordination. Use tsz-ci-pr for failing
checks and queue status.
Rules
- Every PR serves one roadmap goal:
green,fast,grow, orhold. - The PR author manages and lands their own PR; there is no manager or reviewer lane.
- Land-and-continue: push, start the next task, and return to queue the merge when exact-head checks resolve. Never idle-wait on CI.
Before Publish
git status --short --branch
git diff --stat
git diff --check
gh pr list --state open --limit 100 --json number,title,isDraft,headRefName,baseRefName,labels,updatedAt,url
Stage only files in scope.
PR Body
Never rely on --fill alone. Read references/pr-body-checklist.md when
creating or materially editing a body. The pr-body-gate CI job enforces:
Goal: <green|fast|grow|hold>
## Verification
- <commands or CI gates>
## Provenance
Machine: <m1|m4|studio|cloud|hostname>
Assistant: <claude-code|codex|bot>
Model: <model id, e.g. claude-opus-4-8>
Effort: <low|medium|high|max>
Report your actual runtime values (machine, assistant, model, effort); do not invent nicknames.
Verify remote body after create/edit:
gh pr view <number> --json body
WIP, Ready, Reviews
- WIP means draft,
WIPlabel,[WIP]title, or blocker in body. Do not mark ready or queue. - Any WIP/draft/blocker transition needs an immediate comment with reason,
blocker/current work, next action, and verification run, signed with a
provenance line (e.g.
Provenance: studio / claude-code / claude-opus-4-8 / high). - Before marking ready: remove WIP markers, review the latest pushed head, and
update the body's
## Verificationsection to match it. - For substantive reviews: read, react/reply, leave a fix/will-fix/disagree note signed with a provenance line, and update body if scope/risk/ verification changed.
What ships with it
2 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.
- 23d ago First seen · 68 lines · 65 tokens per session scan A a92a18c6f592
tsz-pr-coordination is a skill published in the GitHub repository tsz-org/tsz (577 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 591 once invoked, about $0.0003 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-28.
Other skills, from other repositories
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.