mindforge-review-backlog

mindforge-review-backlog is a skill for Claude Code, Codex from sairam0424/MindForge. It costs 14 tokens per session (479 once invoked), scanned A, original, MIT.

A workflow for reviewing items kept in a project backlog and deciding whether to promote, keep, or remove each one.

In plain words
What is it for?
Listing backlog items, moving selected items into active project phases, and removing rejected items.
Why use it?
It helps turn deferred ideas into ordered roadmap work or clear them out when they are no longer wanted.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

Good fit Listing backlog items, moving selected items into active project phases, and removing rejected items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sairam0424/mindforge/mindforge-review-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 sairam0424/MindForge --skill mindforge-review-backlog
Clone the repo
git clone --depth 1 https://github.com/sairam0424/MindForge

Made for: Claude Code, Codex.

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 mindforge-review-backlog

README.md
[![agentmods](https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-review-backlog/github.svg)](https://agentmods.dev/skills/sairam0424/mindforge/mindforge-review-backlog)
Your own site
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-review-backlog"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-review-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 mindforge-review-backlog

Your own site · 80×15
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-review-backlog"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-review-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 479 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.00014 $0.00479
Opus 5 $0.00007 $0.00239
Sonnet 5 $0.00003 $0.00096
Haiku 4.5 $0.00001 $0.00048

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

Security

Grade A, and why

mindforge-review-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 5d 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.

.agent/skills/mindforge-review-backlog/SKILL.md · 59 lines

What it actually says

  1. List backlog items:

    ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found"
    
  2. Read ROADMAP.md and extract all 999.x phase entries:

    cat .planning/ROADMAP.md
    

    Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.

  3. Present the list to the user via AskUserQuestion:

    • For each backlog item, show: phase number, description, accumulated artifacts
    • Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
  4. For items to PROMOTE:

    • Find the next sequential phase number in the active milestone
    • Rename the directory from 999.x-slug to {new_num}-slug:
      NEW_NUM=$(node ".agent/bin/mindforge-tools.cjs" phase add "${DESCRIPTION}" --raw)
      
    • Move accumulated artifacts to the new phase directory
    • Update ROADMAP.md: move the entry from ## Backlog section to the active phase list
    • Remove (BACKLOG) marker
    • Add appropriate **Depends on:** field
  5. For items to REMOVE:

    • Delete the phase directory
    • Remove the entry from ROADMAP.md ## Backlog section
  6. Commit changes:

    node ".agent/bin/mindforge-tools.cjs" commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
    
  7. Report summary:

    ## 📋 Backlog Review Complete
    
    Promoted: {list of promoted items with new phase numbers}
    Kept: {list of items remaining in backlog}
    Removed: {list of deleted items}
    
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. 5d ago First seen · 59 lines · 14 tokens per session scan A 1688723e730b

Subscribe to this mod's changes

mindforge-review-backlog is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 479 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-09-03.

Related

Other skills, from other repositories

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

reset-epic

Reset an epic's test data — close PRs, delete branches, reopen issues, revert code.

eric-cielo/moflo · 24 tokens

gitlab-ops

Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…

Kanevry/session-orchestrator · 174 tokens

gitlab-portfolio

Use when you need a single-pane cross-repo health view across all vault-registered GitLab and GitHub projects. Discovers repos from overview.md frontmatter in /01-projects//, aggregates open issues, MRs, critical labels, and stale signals via parallel glab/gh calls, then writes an idempotent PORTFOLIO.md dashboard.…

Kanevry/session-orchestrator · 197 tokens

plan

Use this skill when performing structured project planning and PRD generation with three modes: new (project kickoff with repo scaffolding), feature (compact feature PRD), retro (data-driven retrospective). All modes share a researched Q&A engine that dispatches parallel Explore agents before each question wave…

Kanevry/session-orchestrator · 76 tokens

session-plan

Creates a structured wave execution plan with role-based assignment after user alignment. Decomposes agreed tasks into configurable waves (default 5) with optimal agent assignment, dependency ordering, and inter-wave checkpoints. Activated by session-start after Q&A phase completes.

Kanevry/session-orchestrator · 53 tokens