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 skills add flurdy/agent-skills --skill plan-to-backloggit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/plan-to-backlog)<a href="https://agentmods.dev/skills/flurdy/agent-skills/plan-to-backlog"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/plan-to-backlog.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 18 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 188 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 188 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 250 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00054 | $0.04176 |
| Opus 5 | $0.00027 | $0.02088 |
| Sonnet 5 | $0.00011 | $0.00835 |
| Haiku 4.5 | $0.00005 | $0.00418 |
Grade A, and why
plan-to-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 today.
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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan to Backlog
Proposal-first. May recommend no backlog change. Never writes without confirmation.
Turn an approved architecture or implementation plan into the smallest justified durable Beads structure. Inspect the cited plan and existing work, decide whether no item, one focused item, or a bounded epic is warranted, preview the exact write set, then apply only that confirmed proposal.
The canonical behavior and thresholds are defined in the plan-to-backlog contract.
When to use
Select this skill dynamically, or through /plan-to-backlog, only when:
- an
/architector implementation plan has been explicitly approved; - the plan has a stable source or exact capturable session text;
- the user explicitly asks to create or reconcile durable Beads ownership rather than continue planning; and
- no-item versus single-item versus epic is still a meaningful decision.
The existence or approval of a plan alone is not a trigger. Do not use this skill for raw
ideas or Jira intake (/triage), plan refinement (/architect), retrospective backlog
quality (/backlog-groom), or cross-system reconciliation (/tracking-sweep or
/trello-beads).
Usage
/plan-to-backlog <plan-source>
Accepted sources:
- repository or workspace Markdown path;
- Bead ID whose description, design, notes, or linked specification contains the plan;
- Jira or Confluence key/URL when the runtime can retrieve the complete plan; or
- the exact current-session
/architectresult.
There is no invocation that bypasses preview. An initial request to "apply" still follows the full source, proposal, and confirmation procedure.
Ownership boundary
/architectowns technical planning and remains read-only./triageowns unstructured prompt/Jira intake and explicit--human-reviewtracking of pending human decisions; it hands approved implementation plans here without creating children./plan-to-backlogalone owns approved implementation-plan disposition, proposal, confirmation, apply, and recovery. It does not establish ownership of an unapproved human decision./backlog-groomremains retrospective and read-only by default.
What ships with it
9 files 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.
- references/contract.md 19 KB
- scripts/confirmed-bd.sh 5.5 KB runs code
- scripts/sha256-stdin.sh 893 B runs code
- scripts/utc-now.sh 150 B runs code
- tests/fixtures/decision-boundary-scenarios.json 23 KB
- tests/fixtures/decision-scenarios.json 21 KB
- tests/test_decision_fixtures.py 34 KB runs code
- tests/test-helpers.sh 9.9 KB runs code
- tests/test-skill-contract.sh 4.9 KB runs code
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.
- today Changed · +19 lines · -7 tokens per session 53dce01c85e5
- 8d ago First seen · 433 lines · 61 tokens per session scan A 1037fe8d8fa3
plan-to-backlog is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 4,176 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.