Borrowing it
Nothing to install: this file belongs to pvliesdonk/paperless-mcp. 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/pvliesdonk/paperless-mcp/main/.agents/skills/roadmapping/SKILL.mdgit clone --depth 1 https://github.com/pvliesdonk/paperless-mcpWrote 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/skills/pvliesdonk/paperless-mcp/roadmapping)<a href="https://agentmods.dev/skills/pvliesdonk/paperless-mcp/roadmapping"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/roadmapping/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/skills/pvliesdonk/paperless-mcp/roadmapping"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/roadmapping.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.00059 | $0.04344 |
| Opus 5.5 | $0.00024 | $0.01738 |
| Sonnet 5.5 | $0.00012 | $0.00869 |
| Haiku 4.5 | $0.00006 | $0.00434 |
Grade A, and why
roadmapping 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 24d 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.
This is a copy
100% identical to roadmapping — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmapping
A roadmap answers three questions: which direction, in what order, and what we do not yet know. It does not answer how. The moment it starts answering how, it has stopped being a roadmap and has become a plan that will be wrong.
Planning skills have one resolution setting. Point them at six months of work and they produce file paths and schemas for things nobody has looked at yet; reviewers then correctly attack that precision and the whole artefact loses credibility. The fix is to plan at a declared resolution and defend it.
The evidence rule
If you do not have hard evidence, you cannot be certain. It is not your job to obtain that evidence during charting.
An explicit request to research or implement authorizes that work. This rule prevents silently turning a roadmap pass into an investigation; it does not override the user's scope or previously authorized work.
Both halves matter. When you reach a gap, the tempting move is to read the code or open five files until you can say something concrete. Do not. That is how a roadmap fills with confident detail about work nobody has scoped.
Assert it, or file it as a known unknown. Never research to promote it.
Every unknown gets a resolved by pointer: which piece of work, when finished, answers it. When nothing planned will answer it and not knowing changes what you do next, the finding out is itself work: file a research issue (see Everything is work). The evidence rule defers research; it does not cancel it.
The model
Three GitHub objects and one document, each holding one kind of fact. This is the fleet-wide definition; the words mean nothing else here.
| Object | Is | Holds |
|---|---|---|
| Epic | a parent issue with native sub-issues, labelled epic |
the story, its frozen outcome ("Done when"), its children, its refinement issue |
| Package | a milestone titled NNN <content-name> |
the payload of exactly one release cut |
| Issue | a feature, bug, research spike or refinement task, labelled by kind | executable work, at whatever resolution it has earned |
| Index | docs/design/roadmap.md |
the argument: why this direction, why this order, what we do not know |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed · +4 lines ddbd494edd00
- 1mo ago First seen · 386 lines · 59 tokens per session scan A 5648dba5dc2f
roadmapping is a skill published in the GitHub repository pvliesdonk/paperless-mcp (1 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 4,344 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to roadmapping, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
cor-api-tools
Deep reference for all 61 COR MCP API tools — complete argument listings, JSON request/response examples, and common usage patterns for every module.
cor-mcp-server
Main skill for the COR MCP Server — a comprehensive MCP server that exposes 61 Project COR API tools via FastMCP with dual auth (email/password or client credentials), stdio/SSE transport, and auto-refreshing OAuth 2.0.
cor-mcp-setup
Set up and use the COR MCP Server — 61 tools for Project COR (projects, tasks, clients, time tracking, teams). Covers both auth modes: email/password and API key + client secret.
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
build-flow
Create or change a Keboola flow that runs extractors, transformations and writers in order, optionally on a schedule. Use when the user wants to orchestrate, chain or schedule existing Keboola configurations.