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-initnpx skills add Bidiche49/claude-conf --skill backlog-initgit 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-init)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/backlog-init"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-init.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.1 | $0.00013 | $0.00403 |
| Opus 5 | $0.00006 | $0.00201 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
backlog-init 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.
What it actually says
Initialize the BACKLOG/ directory structure for ticket tracking.
Steps
-
Check if
BACKLOG/already exists. If it does, inform the user and stop. -
Create the directory structure:
BACKLOG/ ├── BUGS/{PENDING,DONE}/ ├── FEATURES/{PENDING,DONE}/ ├── IMPROVEMENTS/{PENDING,DONE}/ └── _templates/ -
Create
BACKLOG/_templates/ticket.md— copy from~/.claude/templates/backlog/ticket.mdif it exists, otherwise create it with this content:# [TYPE]-XXX: Titre court **Type:** Bug | Feature | Improvement **Statut:** A faire | En cours | Bloque | Fait **Priorite:** Critique | Haute | Moyenne | Basse **Complexite:** XS | S | M | L | XL **Tags:** [libres, separes par virgule] **Depends on:** none **Blocked by:** — **Date creation:** YYYY-MM-DD --- ## Description [Description claire] ## Fichiers concernes - `path/to/file` ## Criteres d'acceptation - [ ] Critere 1 ## Tests de validation - [ ] Test 1 -
Create
BACKLOG/INDEX.mdwith just the header (it will be fully generated by/backlog-status):# BACKLOG — [project basename] _Run `/backlog-status` to populate this file._ -
Display the created structure to confirm.
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.
- 5d ago First seen · 59 lines · 13 tokens per session scan A 50d2f09a9df2
backlog-init is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 403 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.
react-expert
Expert-level React development with hooks, performance optimization, state management, and modern patterns. Use when the user mentions frontend, hooks, JSX, TypeScript, or Next.js, or when the task involves Modern React, State Management, Forms, or Performance Optimization.
review-pr
Perform a comprehensive code review of a pull request.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.