askit-backlog

askit-backlog is a skill for Claude Code from product-on-purpose/agent-skills-toolkit. It costs 58 tokens per session (529 once invoked), scanned A, original, Apache-2.0.

A backlog-management workflow for maintaining lists of proposed new plugin components and improvements to existing ones.

In plain words
What is it for?
Use it to capture proposals through a why-check, prioritize backlog items, route duplicates, and prune completed or outdated entries.
Why use it?
It helps decide whether a request deserves a new component, belongs as an enhancement, duplicates something already available, or should be removed as stale.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the agent-skills-toolkit plugin — 27 skills, 2 commands, 7 agents, 1 hook, 1 plugin shipped together

Good fit Use it to capture proposals through a why-check, prioritize backlog items, route duplicates, and prune completed or outdated entries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/product-on-purpose/agent-skills-toolkit/askit-backlog
Install

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.

Any agent
npx skills add product-on-purpose/agent-skills-toolkit --skill askit-backlog
Clone the repo
git clone --depth 1 https://github.com/product-on-purpose/agent-skills-toolkit

Made for: Claude Code.

Or install agent-skills-toolkit, the plugin that ships this one along with the rest of its 27 skills, 2 commands, 7 agents, 1 hook, 1 plugin.

Wrote 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.

agentmods badge for askit-backlog

README.md
[![agentmods](https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-backlog/github.svg)](https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-backlog)
Your own site
<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-backlog"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-backlog/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.

agentmods 80×15 button for askit-backlog

Your own site · 80×15
<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-backlog"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 529 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00529
Opus 5 $0.00029 $0.00264
Sonnet 5 $0.00012 $0.00106
Haiku 4.5 $0.00006 $0.00053

Measured 9d ago against content hash a45629372758, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

askit-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 9d 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.

skills/askit-backlog/SKILL.md · 32 lines

What it actually says

askit-backlog

Purpose

Maintain the two local-first backlogs the Standard defines (sec 7.1): docs/internal/backlog/new-components.md (proposals to add a skill, command, subagent, hook, and so on) and docs/internal/backlog/enhancements.md (changes to existing components). Three modes: intake captures a proposal through the why-gate; triage prioritizes and routes; prune removes stale or completed items. Authoring depth is in references/backlog-workflow.md.

When to use

When the user proposes a new component, requests an enhancement, or wants to review, prioritize, or clean the backlog.

intake mode

  1. Decide which backlog: a new component (new-components.md) or a change to an existing one (enhancements.md).
  2. Apply the why-gate to a new-component proposal: is it warranted? is it a duplicate of an existing component, or really a mode of one? what tier and agent-targets? If it fails the gate (a duplicate, or a would-be mode), record the rationale and route it to enhancements instead.
  3. Record the item. New-components: proposed name, component type, target tier, agent-targets, rationale, status. Enhancements: the target component, the change, a why, and a how-to-apply.

triage mode

  1. Review open items; assign priority and, for enhancements, the target component or phase.
  2. Re-route mis-filed items (a "new component" that is really a mode becomes an enhancement).

prune mode

  1. Remove items that shipped (now in the CHANGELOG) or that are stale or rejected, recording why.

Scope

Two backlogs, local-first and version-controlled (sec 7.1): RECOMMENDED at Bronze, REQUIRED at Silver+. The why-gate keeps the new-components backlog from collecting duplicates and would-be modes; consolidation (one skill per component type, modes over micro-skills) is the default answer, per the toolkit's own packaging decision.

Files

What ships with it

2 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.

Changes

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.

  1. 9d ago First seen · 32 lines · 58 tokens per session scan A a45629372758

Subscribe to this mod's changes

askit-backlog is a skill published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 529 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.

Related

Other skills, from other repositories

file-todos

File-based TODO lifecycle for tracking review findings, managing technical debt, and organizing work items. Each TODO is a standalone markdown file with YAML frontmatter, named by convention: {id}-{status}-{priority}-{description}.md. Status transitions drive the lifecycle: pending (created from review) -> ready…

JairoTorregrosa/jaiskills · 143 tokens

help

Get oriented with the solopreneur plugin — see your AI team, check project status, and get suggestions for what to do next. Use when you're getting started or need a refresher.

pcatattacks/solopreneur-plugin · 41 tokens

backlog

Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.

pcatattacks/solopreneur-plugin · 49 tokens

sprint

Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.

pcatattacks/solopreneur-plugin · 29 tokens

standup

Generate a daily standup summary showing what was done, what is planned, and any blockers. Use when the user wants a status update or progress report.

pcatattacks/solopreneur-plugin · 34 tokens

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens