Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. 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/sponge-b0b/Polaris/main/.agents/skills/project-tracking/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/project-tracking)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/project-tracking"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/project-tracking.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.1 | $0.00033 | $0.05661 |
| Opus 5 | $0.00016 | $0.02831 |
| Sonnet 5 | $0.00007 | $0.01132 |
| Haiku 4.5 | $0.00003 | $0.00566 |
Grade A, and why
project-tracking 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 2d 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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Tracking
Reconcile the public Polaris GitHub Project after the owning lifecycle has already established authoritative durable state.
$project-tracking is an internal projection helper. It does not own lifecycle state, delivery focus, scheduling, or correctness.
Invocation Boundary
$project-tracking supports two internal modes.
Formal Artifact Projection
Invoke only:
- from an already-authorized Polaris lifecycle owner after its authoritative tracker/repository transition succeeds; or
- from an explicit reconciliation flow that independently recovered the authoritative durable state.
The caller supplies one or more desired base formal artifact projections. For each artifact provide:
- GitHub issue URL;
Artifact Type;Workflow State;Next Skill— ordinary lifecycle next action before project-delivery overlay;Work Status— ordinary lifecycle status before project-delivery overlay;Areaonly when the caller intentionally owns an Area presentation change;Root BlockerasRB-norNone;Completed OnasYYYY-MM-DDonly whenWorkflow State = Complete, otherwiseNone;Priorityonly when the caller intentionally owns a priority change;- after project-delivery bootstrap,
Project Delivery Statefor every active formal artifact whoseWorkflow Stateis neitherCompletenorSuperseded:in-focus | eligible | blocked | independent.
Artifact Type = Idea and Workflow State = Intake are outside this helper.
Delivery Overlay Sync
Only $project-delivery-management may invoke this mode.
The caller supplies one or more exact open Wayfinder-managed formal artifact URLs plus their current authoritative Project Delivery State: in-focus | eligible | blocked.
This mode does not determine or change lifecycle state. It reads the existing Project row, requires Artifact Type to be one of Wayfinder Map, Wayfinder Decision, Spec, Implementation Ticket, Spec Review, or Review Remediation Ticket, preserves the current projected Workflow State, and reconstructs only the base Work Status and base Next Skill required to re-apply the delivery overlay.
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.
- 2d ago Changed · +20 lines 01de091a774a
- 7d ago First seen · 568 lines · 33 tokens per session scan A 2cda7e414460
project-tracking is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 5,661 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-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…