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 skills add salavender/antigravity-compound-engineering-plugin --skill tracker-routinggit clone --depth 1 https://github.com/salavender/antigravity-compound-engineering-pluginWrote 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/salavender/antigravity-compound-engineering-plugin/tracker-routing)<a href="https://agentmods.dev/skills/salavender/antigravity-compound-engineering-plugin/tracker-routing"><img src="https://agentmods.dev/badge/skills/salavender/antigravity-compound-engineering-plugin/tracker-routing/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/salavender/antigravity-compound-engineering-plugin/tracker-routing"><img src="https://agentmods.dev/badge/skills/salavender/antigravity-compound-engineering-plugin/tracker-routing.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.00000 | $0.00655 |
| Opus 5.5 | $0.00000 | $0.00262 |
| Sonnet 5.5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
tracker-routing 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracker Routing: Linear vs GitHub
Purpose
Route work to the surface that owns its semantic state. Do not create a second project-management layer.
Canonical boundaries
Git docs/specs/ADRs = durable truth
GitHub Issues/PRs = engineering execution + evidence
Linear = temporary attention, brainstorming, decisions, gates
Before creating work
Ask:
- Is this durable knowledge? Write it in the repository.
- Is this executable engineering work? Use GitHub Issues/PRs.
- Is this collaborative reasoning, a business/architecture decision, risk acceptance, or a human gate? Use Linear.
- Does an existing object already cover it?
- Will the object still have value after the canonical Git record exists?
Do not create a Linear issue for every backlog row, probe, log, CI result, or engineering subtask. Do not create a GitHub issue for pure brainstorming.
Linear
Use Linear for:
- product/strategy questions
- architecture alternatives
- hypothesis comparison
- business/risk decisions
- go/no-go gates
- operator attention that requires human action
- temporary multi-agent reasoning
Keep the issue thin. Link to Git documents. Never paste the plan/spec/research body.
When the decision is made:
- write the durable conclusion to Git (
docs/decisions,docs/specs, or the relevant canonical doc); - link any resulting GitHub execution work;
- archive the Linear object when it is no longer an active decision/attention surface.
Auto-synced GitHub projections
If Linear's GitHub Issues Sync creates a GitHub issue for a Linear decision, that GitHub issue is a read-only projection, not engineering work.
- Do not implement it.
- Do not assign engineering agents to it.
- Do not create a branch/PR from it.
- Do not close it independently of the Linear decision while Issues Sync is enabled.
- Prefer disabling GitHub Issues Sync for this repository; keep PR/commit linking enabled.
GitHub
Engineering agents default to GitHub for:
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.
- 1mo ago First seen · 96 lines · 0 tokens per session scan A 2a3023174d0c
tracker-routing is a skill published in the GitHub repository salavender/antigravity-compound-engineering-plugin (48 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 655 tokens. 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
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)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…