Borrowing it
Nothing to install: this file belongs to stoa-platform/stoa. 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/stoa-platform/stoa/main/.claude/skills/sync-plan/SKILL.mdgit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/sync-plan)<a href="https://agentmods.dev/skills/stoa-platform/stoa/sync-plan"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/sync-plan/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/stoa-platform/stoa/sync-plan"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/sync-plan.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.00026 | $0.03323 |
| Opus 5.5 | $0.00010 | $0.01329 |
| Sonnet 5.5 | $0.00005 | $0.00665 |
| Haiku 4.5 | $0.00003 | $0.00332 |
Grade A, and why
sync-plan 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 2mo 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan ↔ Linear Sync (Cycle-Aware)
Synchronize plan.md with Linear ticket statuses using cycle-driven discovery.
Target: $ARGUMENTS
Step 0: Determine Sync Mode
| Argument | Mode | Description |
|---|---|---|
| (empty) | Full sync | Fetch current + next cycle, detect all drift |
CAB-XXXX |
Single ticket | Fetch one ticket, update plan.md marker |
--push |
Push to Linear | Push plan.md markers → Linear statuses |
--cycles |
Cycle discovery | Show current + next cycle summary only |
--velocity |
Velocity report | Show velocity history table + trend + capacity forecast |
Step 1: Fetch Linear Cycles
Always start by discovering the active cycles:
linear.list_cycles(teamId: "<LINEAR_TEAM_ID>")
Identify:
- Current cycle:
type: "current"or dates containing today - Next cycle:
type: "upcoming"or starts after current ends
Extract: cycle ID, name, start date, end date, scope (total issues), completed count.
Step 2: Fetch Cycle Issues
For each active cycle (current + next):
linear.list_issues(
team: "<LINEAR_TEAM_ID>",
cycle: "<cycle_id>",
first: 50
)
For each issue, extract: identifier, title, status, priority (value + name), estimate (value), cycleId, completedAt.
Important: The status field is a string ("Done", "In Progress", "Todo", "Backlog", "Canceled", "Duplicate"), NOT a nested object.
Priority mapping: priority is {value: N, name: "..."} where 1=Urgent, 2=High, 3=Normal, 4=Low.
Estimate mapping: estimate is {value: N, name: "..."} where N is fibonacci points (1,2,3,5,8,13,21,34,55).
Step 3: Parse plan.md
Read plan.md and extract all CAB-XXXX references with their current markers:
| Marker | Meaning |
|---|---|
- [x] |
Done locally |
- [~] |
Partially done |
- [ ] |
Not started or pending |
Extract ticket IDs using pattern: CAB-\d{3,4}
Also identify which cycle section each ticket is in (e.g., "Cycle 7 — CURRENT" vs "Cycle 8 — NEXT").
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.
- 2mo ago First seen · 337 lines · 26 tokens per session scan A 179bb47620b8
sync-plan is a skill published in the GitHub repository stoa-platform/stoa (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 3,323 once invoked, about $0.0001 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-08-31.
sync-plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sync-planstoa-platform/stoa | Skill | 9 | yesterday | Apache-2.0 | A | 26 | Claude Code |
| lyrikgebruder/wirken | Skill | 194 | 2d ago | MIT | A | 15 | Claude Code |
| librariangebruder/wirken | Skill | 194 | 2d ago | MIT | A | 34 | Claude Code |
| notesgebruder/wirken | Skill | 194 | 2d ago | MIT | A | 10 | Claude Code |
| tdx-assetsgebruder/wirken | Skill | 194 | 2d ago | MIT | A | 58 | Claude Code |
| aggregatorgebruder/wirken | Skill | 194 | 2d ago | MIT | A | 30 | Claude Code |
| githubgebruder/wirken | Skill | 194 | 2d ago | MIT | A | 9 | Claude Code |