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.
git clone --depth 1 https://github.com/JunsW/feature-trackWrote 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/plugins/junsw/feature-track/feature-track-claude)<a href="https://agentmods.dev/plugins/junsw/feature-track/feature-track-claude"><img src="https://agentmods.dev/badge/plugins/junsw/feature-track/feature-track-claude/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/plugins/junsw/feature-track/feature-track-claude"><img src="https://agentmods.dev/badge/plugins/junsw/feature-track/feature-track-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
feature-track-claude 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
{
"name": "feature-track",
"version": "0.1.0",
"description": "Lightweight, repo-native shared memory for Claude Code.",
"author": {
"name": "Feature Track contributors"
},
"license": "MIT",
"keywords": [
"ai-agent-memory",
"agent-context",
"claude-code",
"documentation",
"feature-tracking",
"repo-native",
"shared-memory"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 49 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 19 lines scan A 9afbb43695c5
feature-track-claude is a plugin published in the GitHub repository JunsW/feature-track (109 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
deja-vu
deja-vu memory for Claude Code: your own past sessions, from every coding agent on the machine, recalled before you ask.
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and thirty-eight more — searchable and recalled, including work from before it was installed.
ctx
Fast local search and 'git blame' for agent sessions.
basemind
Full AI context layer over MCP — tree-sitter code-map, document RAG (PDF/Office/HTML/email + OCR + reranker), shared agent memory, on-demand web crawl, git history + blame + per-symbol diff. 300+ languages, 10+ coding-agent harnesses, content-addressed Fjall + LanceDB.
basemind
Full AI context layer over MCP — tree-sitter code-map, document RAG (PDF/Office/HTML/email + OCR + reranker), shared agent memory, on-demand web crawl, git history + blame + per-symbol diff. 300+ languages, 10+ coding-agent harnesses, content-addressed Fjall + LanceDB.
greatpractice
A practice for capturing useful ways of working and gradually turning them into shared, repeatable procedures. It is designed to help teams preserve and improve recurring practices over time.