A bug-ticket creator for a project backlog, the list of work waiting to be done. It assigns an ID and records priority, complexity, tags, documentation needs, and likely affected files.

Creating a new BUG-XXX file from a problem description, including details that help someone investigate and fix the bug.

It avoids manually numbering and structuring bug reports, helping keep them consistent and easier to pick up.

backlog-bug — Skill for Claude Code by Bidiche49/claude-conf

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 Bidiche49/claude-conf --skill backlog-bug

Clone the repo

git clone --depth 1 https://github.com/Bidiche49/claude-conf

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-bug/github.svg)](https://agentmods.dev/skills/bidiche49/claude-conf/backlog-bug)

Your own site

<a href="https://agentmods.dev/skills/bidiche49/claude-conf/backlog-bug"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-bug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bidiche49/claude-conf/backlog-bug"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 729 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00729
Opus 5.5	$0.00004	$0.00292
Sonnet 5.5	$0.00002	$0.00146
Haiku 4.5	$0.00001	$0.00073

Measured 1mo ago against content hash 33f224228e82, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backlog-bug 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 1mo 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.

backlog-kit/skills/backlog-bug/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a new BUG ticket in the backlog.

Input

$ARGUMENTS

Steps

Check that BACKLOG/ exists. If not, tell the user to run /backlog-init first and stop.
Calculate the next ID by scanning files (NEVER read INDEX.md for the ID):
- List all files in BACKLOG/BUGS/PENDING/ and BACKLOG/BUGS/DONE/
- Extract all numbers from BUG-XXX.md filenames
- Next ID = max number found + 1 (or 001 if no files exist)
- Format: BUG-XXX (zero-padded to 3 digits)
Analyze the description to determine:
- Priorite (Critique / Haute / Moyenne / Basse)
- Complexite (XS / S / M / L / XL)
- Tags (free-form, relevant to the bug)
Check for external documentation needs: If the bug involves a third-party library, API, or service (e.g. Stripe, Firebase, AWS SDK), note in the ticket that the relevant documentation should be consulted before starting the fix. Add a line in the description: 📖 Consulter: [doc URL or doc name].
Identify affected files: Based on the description and your knowledge of the codebase, determine which files are involved. If you can identify them, list the actual paths. If unsure, list the most likely candidates with a (?) marker. NEVER leave (A determiner) — always make your best assessment.
Write specific acceptance criteria: Describe the expected behavior AFTER the fix. Not "le bug est corrige" — describe what should happen concretely. Example: "La commande install.sh ne crash plus quand le dossier cible n'existe pas" instead of "Le bug est corrige".
Write actionable test steps: List the exact commands to run or manual steps to reproduce/verify. Reference the project's existing test commands when relevant (bash tests/test.sh, bun test, etc.).

Create BACKLOG/BUGS/PENDING/BUG-XXX.md using this format:

# BUG-XXX: [Short title derived from description]

**Type:** Bug
**Statut:** A faire
**Priorite:** [determined]
**Complexite:** [estimated]
**Tags:** [relevant]
**Depends on:** none
**Blocked by:** —
**Date creation:** [today YYYY-MM-DD]

---

## Description
[User's description, enriched with root cause analysis if possible]

## Fichiers concernes
- `path/to/file.ext` — [why this file is involved]

## Criteres d'acceptation
- [ ] [Specific expected behavior after fix]
- [ ] Aucune regression introduite

## Tests de validation
- [ ] [Exact command or manual verification step]

Read the full file on GitHub · 73 lines

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.

1mo ago First seen · 73 lines · 10 tokens per session scan A 33f224228e82

Subscribe to this mod's changes

backlog-bug is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 729 once invoked, about $0.0000 per session on Opus 5.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.

Claude Code Project management anthropic claude cli developer-tools hooks

{{BUCKET}}-management

Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.

damusix/atomic-claude · 0 tokens

config-manager

Skill that manages configuration.

ryo-ebata/cc-audit · 7 tokens

code-review-helper

A safe skill that helps with code review tasks.

ryo-ebata/cc-audit · 13 tokens

system-admin-helper

Skill with dangerous system commands.

ryo-ebata/cc-audit · 9 tokens

vc:team

Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.

opencue/cuecards · 30 tokens

tour-de-controle

Orchestre une tâche complexe en trois temps avec Claude Code — PLANIFIER avec le modèle le plus puissant (Fable 5 / Opus), DÉLÉGUER l'exécution à des sous-agents calibrés lot par lot (Haiku / Sonnet / Opus selon la complexité) lancés en parallèle, puis VÉRIFIER chaque livrable de façon adversariale avec le modèle…

steve-magne/hookstack · 159 tokens