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 commands/openplanr/planr-pipeline/syncgit clone --depth 1 https://github.com/openplanr/planr-pipelineWrote 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/commands/openplanr/planr-pipeline/sync)<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/sync"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/sync.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.00059 | $0.00426 |
| Opus 5 | $0.00030 | $0.00213 |
| Sonnet 5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
sync 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 3d 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
/planr-pipeline:sync [--apply] [--push] [--branch ] [--tracker linear|github|auto]
Read-only by default — never mutates disk or the network unless --apply / --push (or an
explicit confirmation) is given. Fatals use ${CLAUDE_PLUGIN_ROOT}/procedures/fatal-error-format.md.
Execute ${CLAUDE_PLUGIN_ROOT}/procedures/sync-workflow.md — it holds the full contract
(why this exists, the three links it reconciles, the seven HARD RULES, the seven Steps, and
Termination). Both this command and the portable planr-sync skill read that one procedure,
so the sync workflow is implemented exactly once. "Done" is evidenced, never assumed: a spec
is done only when all its internal tasks are done and its ship marker shows
qa_gate_status: passed.
Flags
| Flag | Effect | Default |
|---|---|---|
| (none) | Audit + classified report only. No writes, no network. | on |
--apply |
Apply the SAFE-class fixes locally (status flips, missing wrapper QTs). | off |
--push |
After --apply, push changed QTs to the tracker, then git commit (+ push). |
off |
--branch <name> |
Branch to operate on. | auto-detect |
--tracker <t> |
Force linear / github; auto uses whatever the project configures. |
auto |
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.
- 3d ago First seen · 26 lines · 59 tokens per session scan A 79640cec2401
sync is a command published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 29d ago), licensed MIT. It adds 59 tokens to every session and 426 once invoked, about $0.0003 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 commands, from other repositories
codebase-audit
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
project-sprint
Execute project-sprint through Core-owned bounded WorkUnits.
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
whats-next
Show current project status and suggest next steps.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.