What is feature-track-validate?

A command that checks whether Feature Track documentation follows the project's required format and rules.

Use it to validate Feature Track documents locally or run stricter checks intended for CI.

It finds documentation problems before they reach review or continuous integration, where automated checks run on submitted code.

feature-track-validate — Command by JunsW

Install

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.

agentmods

npx agentmods add commands/junsw/feature-track/feature-track-validate

Clone the repo

git clone --depth 1 https://github.com/JunsW/feature-track

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 59 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.00059
Opus 5	$0.00000	$0.00030
Sonnet 5	$0.00000	$0.00012
Haiku 4.5	$0.00000	$0.00006

Measured 3d ago against content hash 2f8716d7a224, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-track-validate 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 3d 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.

skills/claude-code/commands/feature-track-validate.md · 17 lines

What it actually says