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/scharissis/polako/plan-backlognpx skills add scharissis/polako --skill plan-backloggit clone --depth 1 https://github.com/scharissis/polakoWrote 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/scharissis/polako/plan-backlog)<a href="https://agentmods.dev/skills/scharissis/polako/plan-backlog"><img src="https://agentmods.dev/badge/skills/scharissis/polako/plan-backlog.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03552 |
| Opus 5 | $0.00000 | $0.01776 |
| Sonnet 5 | $0.00000 | $0.00710 |
| Haiku 4.5 | $0.00000 | $0.00355 |
Grade A, and why
plan-backlog 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 yesterday.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose a backlog from $vision
Focus, if one was given: $focus
What this run may do, and what it may not
It reads a repository and files proposals: issues carrying the proposed
label, which no unattended run will ever pick up. A human takes that label off,
and that act — not this run — is what queues work.
So the whole of the write surface is creating labelled issues. This run does not commit, push, open pull requests, alter existing issues or comments, or touch a line of code. If something here seems to call for one of those, the answer is that it belongs in a proposal for a human to approve, not in this run.
The whole of the gh surface this run may use, today, is three call shapes:
the two issue list reads in Phase 0, and the one issue create in Phase 4 —
the last of which may carry --parent and --blocked-by, and no other write
flag. Nothing else, including anything that looks like diligence rather than a
write: do not run gh label list to confirm the proposed label exists, or
gh --version, or any other pre-flight probe. Assume the label exists — it is
the label this skill mints every issue with. The allowlist is the binary's to
grant, not this skill's to widen: polako plan grants this run its tools,
polako health grants its twin review-health only issue list and issue create, and an operator's -tools can narrow either verb further. issue list and issue create are the floor every shipped verb grants, so they are
the only surface this skill can rely on — a call outside them raises a
permission prompt nobody is there to answer under an unattended drain, and the
run hangs instead of reporting. Improvising one, however reasonable it looks,
is worse than skipping a check that was never asked for.
The document is required
If $vision is empty, stop and ask which document to work from. Never guess which file is the roadmap: picking the wrong one produces a plausible backlog for a project nobody is building, and the mistake is invisible until a curator reads seven issues that make no sense.
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.
- yesterday Changed · +32 lines 3908b166ec36
- 4d ago First seen · 241 lines · 0 tokens per session scan A 91ad68fd31b7
plan-backlog is a skill published in the GitHub repository scharissis/polako (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,552 tokens. 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
pm-portfolio-v1
Portfolio and roadmap batch intake, turn a pile of asks into a prioritised verdict. Use when someone hands a BATCH and wants a decision: "prioritise this backlog", "score these requests", "batch verdict", "what goes in the next sprint or quarter", "turn this backlog document into a roadmap", "sprint recommendation"…
compound
Document solved problems to compound team knowledge. Creates categorized docs with YAML frontmatter. Triggers on "that worked", "it's fixed", "compound".
research
Conduct comprehensive codebase research producing a persistent document. Use when you need to understand something BEFORE planning, or for pure exploration. Triggers on "research", "investigate", "explore codebase".
plan-eng-review
Engineering plan review. Reviews a plan document for architecture, code quality, test coverage, and performance before implementation begins. Produces a coverage diagram, failure modes map, and parallelization strategy. Use when asked to "review this plan", "eng review", or "architecture review".
authoring-prd
Use when turning a product idea or change into a loop-ready continuous backlog with small stories and executable behavioral evidence.
writing-for-agents
Create or edit agent-facing instructions such as AGENTS.md, CLAUDE.md, skills, roles, and workflow documents. Use when triggers, completion criteria, context pointers, instruction hierarchy, or duplication affect whether an agent can execute the document reliably.