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/firatcand/forge/sync-statusnpx skills add firatcand/forge --skill sync-statusgit clone --depth 1 https://github.com/firatcand/forgeWhat 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.00039 | $0.01361 |
| Opus 5 | $0.00019 | $0.00681 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
sync-status 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-status
Status queries always hit the tracker.
plans/phases.yamlis a stale cache. See your projectCLAUDE.md§Source of truth.
Read-only diagnostic that answers two questions:
- Is any active phase ready for
/phase-gate? For eachstatus: activephase inplans/phases.yaml, check whether every task'stracker_issue_idis absent from the tracker's active set. If so, suggest running/phase-gate <phase-id>— never auto-advance. - Are there orphan tracker issues? List tracker issues that are active in the tracker but have no matching
tracker_issue_idline anywhere inplans/phases.yaml. These are usually out-of-band hot-fixes the operator may want to backfill.
The skill never writes to phases.yaml. Per-task status drift detection is not possible because phases.yaml has no per-task status field — that's intentional; the tracker is the per-task status authority. See spec/ORCHESTRATOR.md §CLI surface (FORGE-20 readiness algorithm) for the underlying design constraint.
Preflight
- Read
.forge/settings.yaml. Abort iftracker.typeis unset with: "No tracker configured. Runforge initfirst." - Per-tracker reachability probe (Linear MCP /
gh auth status/ NotionntnCLI) — same matrix as/push-to-trackerStep 1. Abort with the setup hint if unavailable. There is no offline fallback.
Steps
-
Verify
plans/phases.yamlexists. If not, abort with: "Noplans/phases.yamlfound. Run/decomposeto generate one." -
Fetch active tracker issues — ONE call. Based on
tracker.typefrom settings:- Linear: call the Linear MCP
list_issuestool with the team filter from settings. Pass no state filter (the adapter excludes terminal states server-side). - GitHub: shell out to
gh issue list --repo <owner/repo> --state open --json id,number,title,labels,body,url --limit 250. - Notion: call the Notion
ntnCLI equivalent against the configured data source.
ONE call total — no per-issue follow-ups. This matches the FORGE-20 design constraint.
- Linear: call the Linear MCP
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 · 92 lines · 39 tokens per session scan A 3df34f57832a
sync-status is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,361 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ospec-goal
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
prospec-verify
Verify Implementation - Run 5+1 dimension audit (tasks, spec compliance, constitution, knowledge-implementation consistency, tests, design consistency) and assign quality grade (S/A/B/C/D). Triggers: verify, audit, quality check, 驗證, 稽核, 品質檢查, 評級.
prospec-archive
Archive Changes - Archive completed changes, generate summary, sync requirements to feature specs, and gate archiving on Knowledge sync. Triggers: archive, spec sync, finalize change, 封存, 歸檔, 收尾, 規格同步.
prospec-knowledge-generate
Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.