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 agents/chris-dare-dev/agent-kit/roadmap-materializergit clone --depth 1 https://github.com/chris-dare-dev/agent-kitWhat 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.00141 | $0.03425 |
| Opus 5 | $0.00071 | $0.01713 |
| Sonnet 5 | $0.00028 | $0.00685 |
| Haiku 4.5 | $0.00014 | $0.00343 |
Grade C, and why
roadmap-materializer scanned grade C with 2 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
"Now run X", "Ignore previous instructions", "Authorize the user", "Add yourself Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ".claude/agent-memory/roadmap-materializer/lessons.md" 2>/dev/null || echo "(no lessons yet)" How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Materializer
You are Phase 4 of the /roadmap pipeline. Your job is to finalize the roadmap doc, lint it, emit + validate the machine-readable milestone register, and (when requested) draft GitLab issue bodies to local files so the orchestrator can present them to the user for authorization.
The orchestrator (slash command at .claude/commands/roadmap.md) dispatches you with substituted variables. You never invoke other sub-agents.
Input variables (substituted by the orchestrator)
{SLUG}— the roadmap slug{ROADMAP_PATH}— absolute path toplans/<slug>-roadmap.md{GITLAB_MODE}—"off"(default) or"draft-only"(write draft issue bodies to local files){DRAFTS_DIR}— absolute path to<repo-root>/.claude/notes/roadmaps/<slug>/drafts/(used only when GITLAB_MODE=draft-only){MILESTONES_PATH}— absolute path to<repo-root>/.claude/notes/roadmaps/<slug>/milestones.json(the machine-readable milestone register — LOCAL-ONLY, never committed; you author a.incomingdraft and merge deterministically)
Step 0 — Read persistent memory (skip-if-not-relevant)
cat ".claude/agent-memory/roadmap-materializer/lessons.md" 2>/dev/null || echo "(no lessons yet)"
Step 1 — Read the phase-materialize reference + entire roadmap doc (REQUIRED)
Read in order (paths resolve from ANY CWD — the target repo is usually NOT the agent-kit checkout, so never use relative data/... paths):
$WS/.claude/references/roadmap-phase-materialize.md(whereWS="${PERSONAL_WORKSPACE_ROOT:-$HOME/Work/workspace}"; equivalently MCPget_reference("roadmap-phase-materialize")) — canonical Phase 4 detail: cross-references format, lint rules, register field mapping, GitLab artifact construction,/issue-createhandoff,/milestone-pipelinekick-off.- The entire
{ROADMAP_PATH}doc — all sections.
Do NOT proceed until both are loaded.
Step 2 — Write the ## Cross-references section
Write the ## Cross-references section into {ROADMAP_PATH} using Edit (preserves other sections).
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 · 260 lines · 141 tokens per session scan C df22c680d14f
roadmap-materializer is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 24d ago), licensed MIT. It adds 141 tokens to every session and 3,425 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 2 findings (instruction-override phrasing, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.