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/JunsW/feature-tracknpx agentmods add commands/junsw/feature-track/feature-track-initWrote 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/commands/junsw/feature-track/feature-track-init)<a href="https://agentmods.dev/commands/junsw/feature-track/feature-track-init"><img src="https://agentmods.dev/badge/commands/junsw/feature-track/feature-track-init/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/commands/junsw/feature-track/feature-track-init"><img src="https://agentmods.dev/badge/commands/junsw/feature-track/feature-track-init.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.00000 | $0.00058 |
| Opus 5.5 | $0.00000 | $0.00023 |
| Sonnet 5.5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
feature-track-init 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.
What it actually says
feature-track-init
Initialize Feature Track in this repository.
Run:
python3 cli/feature_track.py init --root .
If the CLI is not present, create docs/features/README.md from the Feature Track index template and 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.
- 1mo ago First seen · 13 lines · 0 tokens per session scan A ab18c86f2643
feature-track-init is a command published in the GitHub repository JunsW/feature-track (109 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 58 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
ng-deficiency
Portable command prompt generated from skills/tracking-deficiencies/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
backlog
PitWay: Capture out-of-scope work discovered mid-task, without expanding current scope.
work
Work unit management: list, continue, checkpoint, switch.
setup:transitions
Add hourly session progress tracking to existing project (migration command - retire when all projects updated).
status
Report Shipshape deck state derived from repository signals. Read-only.
aitask-pr-import
Create an aitask from a pull request by analyzing PR data and generating a structured task with implementation plan.