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 skills add Bidiche49/claude-conf --skill backlog-statusgit 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-status)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/backlog-status"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-status/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.
<a href="https://agentmods.dev/skills/bidiche49/claude-conf/backlog-status"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/backlog-status.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00505 |
| Opus 5.5 | $0.00005 | $0.00202 |
| Sonnet 5.5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
backlog-status 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.
What it actually says
Scan all tickets and regenerate INDEX.md from scratch. Then display stats.
Steps
-
Check that
BACKLOG/exists. If not, inform the user and stop. -
Scan all ticket files in:
BACKLOG/BUGS/PENDING/andBACKLOG/BUGS/DONE/BACKLOG/FEATURES/PENDING/andBACKLOG/FEATURES/DONE/BACKLOG/IMPROVEMENTS/PENDING/andBACKLOG/IMPROVEMENTS/DONE/
-
For each ticket file, read and extract:
- ID and title (from the
# TYPE-XXX: Titleheading) - Priorite (from the
**Priorite:**field) - Statut: "A faire" if in PENDING/, "Fait" if in DONE/
- ID and title (from the
-
Rewrite
BACKLOG/INDEX.mdentirely with this format:# BACKLOG — [basename of project directory] ## FEATURES | ID | Titre | Statut | Priorite | |----|-------|--------|----------| | FEAT-001 | ... | A faire | Haute | **Prochain ID : FEAT-XXX** ## BUGS | ID | Titre | Statut | Priorite | |----|-------|--------|----------| **Prochain ID : BUG-XXX** ## IMPROVEMENTS | ID | Titre | Statut | Priorite | |----|-------|--------|----------| **Prochain ID : IMP-XXX**- Sort tickets by ID within each section
- "Prochain ID" = max ID found + 1 (or 001 if no tickets). Zero-padded to 3 digits.
- If a section has no tickets, leave the table empty (header only)
-
Display stats in the terminal:
BACKLOG STATUS ══════════════ BUGS: X pending / X done FEATURES: X pending / X done IMPROVEMENTS: X pending / X done ────────────── TOTAL: X pending / X done
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 · 65 lines · 12 tokens per session scan A 7213dcd6f8e8
backlog-status is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 505 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.
Other skills, from other repositories
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
config-manager
Skill that manages configuration.
code-review-helper
A safe skill that helps with code review tasks.
system-admin-helper
Skill with dangerous system commands.
vc:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.
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…