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/bidiche49/claude-conf/backlog-bugnpx skills add Bidiche49/claude-conf --skill backlog-buggit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/bidiche49/claude-conf/backlog-bug)<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="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.00010 | $0.00729 |
| Opus 5 | $0.00005 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
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 4d 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.
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-initfirst and stop. -
Calculate the next ID by scanning files (NEVER read INDEX.md for the ID):
- List all files in
BACKLOG/BUGS/PENDING/andBACKLOG/BUGS/DONE/ - Extract all numbers from
BUG-XXX.mdfilenames - Next ID = max number found + 1 (or 001 if no files exist)
- Format:
BUG-XXX(zero-padded to 3 digits)
- List all files in
-
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.shne 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.mdusing 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]
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.
- 4d ago First seen · 73 lines · 10 tokens per session scan A 33f224228e82
backlog-bug is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 729 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-08-31.
Other skills, from other repositories
hooks-eval
Evaluate hook security, performance, and SDK compliance. Use for audits.
webmcp-setup
Bootstraps webmcp-react into an existing React or Next.js app. Installs dependencies, adds WebMCPProvider, creates a first tool, and configures the MCP client bridge. Use when the user wants to set up WebMCP, add MCP tools to their app, integrate webmcp-react, or make their React app accessible to AI agents.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
review-pr
Perform a comprehensive code review of a pull request.
talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.
guide-recap
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate release notes, announcements, social media posts, or recap summaries from guide updates.