Borrowing it
Nothing to install: this file belongs to asynkron/Asynkron.JsEngine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/asynkron/Asynkron.JsEngine/main/.claude/commands/roadmap.mdgit clone --depth 1 https://github.com/asynkron/Asynkron.JsEngineWrote 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/asynkron/asynkron.jsengine/roadmap)<a href="https://agentmods.dev/commands/asynkron/asynkron.jsengine/roadmap"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/roadmap/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/asynkron/asynkron.jsengine/roadmap"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/roadmap.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.00007 | $0.02187 |
| Opus 5.5 | $0.00003 | $0.00875 |
| Sonnet 5.5 | $0.00001 | $0.00437 |
| Haiku 4.5 | $0.00001 | $0.00219 |
Grade A, and why
roadmap 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Generator
Generate a hierarchical markdown roadmap from all GitHub issues and update/create the Roadmap issue.
Process
1. Fetch all open issues
gh issue list --state open --limit 500 --json number,title,labels,body
2. Enforce naming conventions
Before generating the roadmap, ensure all issues follow consistent naming:
Naming Rules
| Label | Required Prefix | Example |
|---|---|---|
epic |
Epic: |
Epic: IR-only Execution |
bug |
Bug: |
Bug: strict mode block function scoping |
| (tasks) | Task X.Y: |
Task 0.1: Add AST-free assertion guard |
Task Numbering Convention
- Top-level tasks under an epic:
Task 1:,Task 2:, etc. - Subtasks use dot notation:
Task 1.1:,Task 1.2:,Task 2.1:, etc. - Deeper nesting:
Task 1.1.1:,Task 1.1.2:, etc.
Rename issues that don't follow conventions
For each issue that needs renaming:
gh issue edit <number> --title "<corrected title>"
Common renames needed:
Phase 0 —→Task 0:Phase 1 —→Task 1:P0.1:→Task 0.1:P1.2:→Task 1.2:bug:(lowercase) →Bug:- Missing
Epic:prefix on epic-labeled issues
3. Categorize and organize issues
Parse each issue and categorize:
- Bugs: Issues with
buglabel (must haveBug:prefix) - Epics: Issues with
epiclabel (must haveEpic:prefix) - Tasks: All other issues (must have
Task X.Y:prefix)
For hierarchy, analyze:
- Task numbering patterns (e.g.,
Task 0,Task 1.2) - Issue body for references to other issues (
Parent: #123,Blocked by #456) - Labels indicating parent/child relationships
- Semantic grouping by feature area or component
3.1 Analyze and consolidate related bugs
Important: Before listing bugs, analyze them to find related issues that share the same root cause.
- Read each bug's body to understand:
- The error message / exception type
- The stack trace location
- The test or scenario that triggers it
- Any "Related" or "See also" references
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.
- 14d ago First seen · 236 lines · 7 tokens per session scan A 8356f37f7b8a
roadmap is a command published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 2,187 once invoked, about $0.0000 per session on Opus 5.5. 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-10-02.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.