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 commands/junsw/feature-track/feature-track-addgit clone --depth 1 https://github.com/JunsW/feature-trackWhat 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.00000 | $0.00107 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
feature-track-add 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 yesterday.
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.
What it actually says
feature-track-add
Create a Feature Track entry for a feature.
Expected argument: a lowercase hyphen-case feature id, for example checkout.
Run:
python3 cli/feature_track.py add "$ARGUMENTS" --root .
If the CLI is not present, create docs/features/<feature-id>/README.md plus prd/, api/, plans/, and archive/, then add a row to docs/features/README.md. Do not overwrite existing files.
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.
- yesterday First seen · 15 lines · 0 tokens per session scan A 082664e4de23
feature-track-add is a command published in the GitHub repository JunsW/feature-track (107 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 107 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 commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-x
Audit or improve X/Twitter profile and posting strategy.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
ng-red-team
Portable command prompt generated from skills/stress-testing-agent-changes/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.