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/stoa-platform/stoa/roadmapnpx skills add stoa-platform/stoa --skill roadmapgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00024 | $0.01621 |
| Opus 5 | $0.00012 | $0.00811 |
| Sonnet 5 | $0.00005 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
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 3d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Visibility — Strategic Progress Snapshot
Display or generate STOA Platform roadmap aligned with Linear roadmap:* labels and milestones.
Target: $ARGUMENTS
Step 0: Determine Mode
| Argument | Mode | Description | MCP Budget |
|---|---|---|---|
| (empty) | Snapshot | Display roadmap in terminal (read-only) | 7-8 reads |
--update |
Update | Regenerate ROADMAP.md at repo root |
7-8 reads + 1 file write |
--milestones |
Milestones | Show milestone timeline with days remaining | 1 MCP read |
Step 1: Fetch Theme Progress (5 queries)
Query each roadmap:* label to count Done vs Total issues:
For each theme in [gateway, platform, dx, security, community, observability]:
linear.list_issues(
team: "<LINEAR_TEAM_ID>",
labels: ["roadmap:<theme>"],
first: 250
)
Count: total issues, done issues (status = "Done" or "Canceled")
Label IDs (cached)
| Theme | Label | ID |
|---|---|---|
| Gateway | roadmap:gateway |
<LABEL_ID_ROADMAP_GATEWAY> |
| Platform | roadmap:platform |
<LABEL_ID_ROADMAP_PLATFORM> |
| DX | roadmap:dx |
<LABEL_ID_ROADMAP_DX> |
| Security | roadmap:security |
<LABEL_ID_ROADMAP_SECURITY> |
| Community | roadmap:community |
<LABEL_ID_ROADMAP_COMMUNITY> |
| Observability | roadmap:observability |
<LABEL_ID_ROADMAP_OBSERVABILITY> |
Important: Theme percentages depend on roadmap:* labels being applied to issues. If a theme shows 0/0, it means no issues have been tagged with that label yet. Run a backfill session to tag historical issues.
Step 2: Fetch Milestones (1 query)
linear.list_milestones(project: "<LINEAR_PROJECT_ID>")
Milestone IDs (cached)
| Milestone | ID | Target Date |
|---|---|---|
| Demo MVP Ready | <MILESTONE_DEMO_MVP> |
2026-02-17 |
| Demo Day | <MILESTONE_DEMO_DAY> |
2026-03-17 |
| Private Beta | <MILESTONE_PRIVATE_BETA> |
2026-04-30 |
| RC1 Public Beta | <MILESTONE_RC1> |
2026-06-30 |
| v1.0 GA | <MILESTONE_V1_GA> |
2026-07-31 |
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.
- 3d ago First seen · 165 lines · 24 tokens per session scan A c0e499f67a33
roadmap is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 1,621 once invoked, about $0.0001 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-31.
Other skills, from other repositories
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
csv-tools
Parse and analyze CSV data.