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 skills/yoursshlabs/yourssh/yourssh-roadmapnpx skills add YoursshLabs/yourssh --skill yourssh-roadmapgit clone --depth 1 https://github.com/YoursshLabs/yoursshWhat 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.00053 | $0.01093 |
| Opus 5 | $0.00026 | $0.00547 |
| Sonnet 5 | $0.00011 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00109 |
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 2d 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 — 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.yamlchanges
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 roadmapBash git log --oneline -30— recent commitsBash grep -E "^version:" app/pubspec.yaml— current versionBash ls app/lib/providers app/lib/services app/lib/widgets packages/— surface area of existing codeBash 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)
- Version line:
-
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
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.
- 2d ago First seen · 89 lines · 53 tokens per session scan A f4891f72700e
yourssh-roadmap is a skill published in the GitHub repository YoursshLabs/yourssh (40 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 1,093 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…