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.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.00012 | $0.00505 |
| Opus 5 | $0.00006 | $0.00253 |
| Sonnet 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 7d 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.
- 7d 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 4mo ago), licensed MIT. It adds 12 tokens to every session and 505 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
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.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.
expo-eas-submit
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production…
consulting
Strategic consulting skills for organizations. Long-term planning, business strategy, change management, organizational design, competitive analysis, vision/mission frameworks. Triggers on: strategy, consulting, planning, organizational change, competitive analysis, business model, vision.