What is yourssh-roadmap?

A project-specific process for refreshing a yourssh project's roadmap file, which is a document listing shipped work and planned work. It compares the current code, recent Git history, releases, and version information with the existing roadmap.

Use it after shipping a major feature, merging work, releasing a new version, or asking to refresh the yourssh project's roadmap.

It helps keep the roadmap aligned with what has actually been built, rather than relying on outdated planning notes. It updates the existing document by identifying completed work and remaining items.

How YoursshLabs/yourssh configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to YoursshLabs/yourssh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/YoursshLabs/yourssh/master/.claude/skills/yourssh-roadmap/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/YoursshLabs/yourssh

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yoursshlabs/yourssh/yourssh-roadmap/github.svg)](https://agentmods.dev/skills/yoursshlabs/yourssh/yourssh-roadmap)

Your own site

<a href="https://agentmods.dev/skills/yoursshlabs/yourssh/yourssh-roadmap"><img src="https://agentmods.dev/badge/skills/yoursshlabs/yourssh/yourssh-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yoursshlabs/yourssh/yourssh-roadmap"><img src="https://agentmods.dev/badge/skills/yoursshlabs/yourssh/yourssh-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.1	$0.00053	$0.01093
Opus 5.5	$0.00021	$0.00437
Sonnet 5.5	$0.00011	$0.00219
Haiku 4.5	$0.00005	$0.00109

Measured 2mo ago against content hash f4891f72700e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

yourssh-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 2mo 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.

.claude/skills/yourssh-roadmap/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

YourSSH Roadmap Refresh

Update docs/roadmap.md for the yourssh repo based on the actual state of the codebase + git history. Avoid rewriting the roadmap from scratch each time — only diff what already exists and propose new features.

When to use

User says "update roadmap", "refresh roadmap", "cập nhật roadmap", "version bump xong rồi"
After merging a large feature into develop/master
When prepping for sprint planning
When the version in app/pubspec.yaml changes

Do not use when: the user wants to brainstorm completely new features from scratch (use superpowers:brainstorming) or write a spec for a specific feature (use superpowers:writing-plans).

Workflow

Read current state (run in parallel):
- Read docs/roadmap.md — existing roadmap
- Bash git log --oneline -30 — recent commits
- Bash grep -E "^version:" app/pubspec.yaml — current version
- Bash ls app/lib/providers app/lib/services app/lib/widgets packages/ — surface area of existing code
- Bash git tag --sort=-creatordate | head -10 — shipped releases
Classify shipped vs remaining by comparing commit messages + new file names against the old roadmap list. Move shipped bullets up to the "Shipped" section at the top of the doc.
Update metadata:
- Version line: Current version: X.Y.Z
- Date line: updated: YYYY-MM-DD (use the real date, do not hard-code)
Ask the user one question (via AskUserQuestion):
- Are there new features to add to P0/P1/P2?
- Is there anything to re-prioritize?
- If the user says "no, just update what's shipped" → skip step 5.
Apply user changes (if any) into the correct table/section.
Show diff before committing: Bash git diff docs/roadmap.md. Wait for user approval before suggesting a commit.

Roadmap structure (must be preserved)

# YourSSH — Roadmap
> Direction + version + date
[Section "Shipped"]
## P0 — Must-have to retain power users  (table with 10 rows)
## P1 — Differentiation & DevOps depth  (sub-sections by theme)
## P2 — Team / Enterprise
## Top 3 suggestions for the next sprint
## How to use this document

Read the full file on GitHub · 89 lines

Changes

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.

2mo ago First seen · 89 lines · 53 tokens per session scan A f4891f72700e

Subscribe to this mod's changes

yourssh-roadmap is a skill published in the GitHub repository YoursshLabs/yourssh (43 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,093 once invoked, about $0.0002 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-08-30.

Planning

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

yourssh: Skill for Claude Code