Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bks-lab/open-bridgenpx agentmods add skills/bks-lab/open-bridge/tracker-syncWrote 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/bks-lab/open-bridge/tracker-sync)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/tracker-sync"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/tracker-sync/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/bks-lab/open-bridge/tracker-sync"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/tracker-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.01475 |
| Opus 5.5 | $0.00033 | $0.00590 |
| Sonnet 5.5 | $0.00017 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
tracker-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 22d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracker-Sync
Keeps The Bridge's task state and the GitHub Project boards aligned, with a
persistent local snapshot as the pivot. Three deterministic engine
subcommands (scripts/tracker-sync.py — a shared repo-root utility shipped
with the Bridge repo itself, not a file inside this skill's own directory)
plus one gated write path.
Provider scope: GitHub Projects V2 only for now — other trackers
(e.g. ADO) are readable via trackers/*.md playbooks but are not
covered by snapshot/diff/push.
Model — remote-authoritative. The team works in GitHub, so the board owns shared status. The Bridge mirrors it, surfaces drift, and stages your pushes. Pull is autonomous (read-only); every cross-write is a proposal:
- never auto-write STATUS.md (a human decides what a remote change means)
- never auto-push to GitHub (gated, batch-confirmed, via github-projects-manager)
When to use
- "sync my tasks", "which task is in which state"
- "pull the boards", "snapshot the projects", "give me a board dump"
- before/after working a board, to see what drifted
/briefingcalls the pull side automatically (see references/workflow.md)
Subcommands (verbs)
| Verb | What | Gate |
|---|---|---|
pull |
refresh snapshots from all enabled GitHub boards | autonomous (read-only) |
status / diff |
render the delta table (the control surface) | read-only |
push |
apply local_ahead rows to GitHub |
gated, via github-projects-manager |
sync |
pull → diff → offer push |
gated at the push step only |
How to run
pull (down — autonomous)
python3 scripts/tracker-sync.py pull # all boards from ecosystem.yaml
python3 scripts/tracker-sync.py pull --project <slug>
Writes work/trackers/github/<slug>.json + work/trackers/_index.yaml with a
pulled_at stamp. Best-effort: if gh is missing/unauthed it warns and skips —
never blocks. The git history of work/trackers/ IS the dated dump history.
diff (the cockpit — read-only)
python3 scripts/tracker-sync.py diff # table
python3 scripts/tracker-sync.py diff --format json
python3 scripts/tracker-sync.py diff --exit-code # exit 2 if actionable drift
Each row is one linked issue, classified (see references/diff-model.md). Present the table, then offer the obvious next action per class:
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.
- 22d ago Changed · -9 lines · -93 tokens per session 608b3e0cb8eb
- 1mo ago First seen · 124 lines · 176 tokens per session scan A fb4473a06752
tracker-sync is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,475 once invoked, about $0.0003 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
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
pr-shepherding
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
team-pr
Use for opening PRs only on explicit request. Never infer from passed verification. Includes project terms, evidence, and risk.