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/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/sponge-b0b/polaris/project-tracking"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/project-tracking.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.00028 | $0.01817 |
| Opus 5.5 | $0.00011 | $0.00727 |
| Sonnet 5.5 | $0.00006 | $0.00363 |
| Haiku 4.5 | $0.00003 | $0.00182 |
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 7d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Tracking
$project-tracking is a deterministic, non-authoritative projection helper.
It does not own lifecycle state, semantic authority, delivery focus, scheduling, dependencies, hierarchy, completion, or artifact membership semantics.
Invocation boundary
Project projection is intentionally eventually consistent during active delivery. Invoke this helper only at:
- Mandatory Spec completion reconciliation —
$spec-merge-cleanupreconstructs the complete completed-Spec lineage and supplies one desired projection batch. - Explicit human-requested board reconciliation — the active workflow reconstructs the requested authoritative artifact universe and supplies one desired projection batch.
Ordinary lifecycle transitions do not synchronize the Project. Do not persist a pending Project-update queue/flag/label/comment ledger.
Repository/Project setup, schema changes, historical backfills, or other administrative conversion work are outside this runtime skill.
Input contract
The caller supplies one desired base projection per formal artifact:
- GitHub issue URL;
Artifact Type;Workflow State;- base
Next Skill; - base
Work Status; Completed Ononly forComplete;- current
Project Delivery Statefor every active formal artifact:in-focus | eligible | blocked | independent; - optional
Area/Priorityonly when the caller intentionally owns those presentation changes.
The caller reconstructs the complete authoritative artifact universe. This skill never crawls Project rows to decide what ought to exist.
Authority rules
Never infer lifecycle/delivery truth from:
- Project fields or membership;
- issue open/closed state alone;
- labels;
- saved-view position;
- hierarchy alone;
- prior conversation.
Project state is read only to detect and repair projection drift.
Delivery context comes from $project-delivery-management for Wayfinder-managed artifacts
or explicit durable Independent classification. Ambiguous governance is invalid rather than
silently treated as Independent.
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.
- 7d ago Changed · -326 lines · +28 tokens per session 612d677b3a97
- 8d ago Changed · +20 lines 405ff74b9674
- 1mo ago Changed · +14 lines be73dd9b24cf
- 1mo ago Changed · -49 lines · -33 tokens per session 2d637752aeea
- 1mo ago Changed · +20 lines 01de091a774a
- 1mo 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 today), licensed Apache-2.0. It adds 28 tokens to every session and 1,817 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.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
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.
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.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
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 zai-glm-flash smoke test), open code review (ocr)…