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/lucassantana-dev/sharekit/backlognpx skills add LucasSantana-Dev/sharekit --skill backloggit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWhat 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.00062 | $0.01341 |
| Opus 5 | $0.00031 | $0.00671 |
| Sonnet 5 | $0.00012 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
backlog 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 2d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/backlog
End-to-end backlog builder for a single repo. Turns "what's wrong or missing here?" into a curated, ROI-ranked, deduped set of GitHub issues on a Project board — with full specs for new features and a propose-then-confirm gate before any GitHub write.
Replaces: /audit-deep, /repo-state-snapshot, /ecosystem-health,
/adt-specs-spec-new, /plan-to-issues, and manual board management.
When this fires
Auto-invoked on: "build a backlog", "what should I work on", "audit and plan",
"sprint planning", "I have N days", and similar queries. Also auto-queued by
/onboard-new-repo and auto-queues /next-priority at completion.
See references/workflow.md § Triggers for the full auto-invoke list.
Eight-phase workflow
Runs sequentially with parallel discovery in Phase 1. Each phase has explicit stop/skip conditions and a reconciliation line — never silently omit.
Phase summary:
-
Phase 0: RAG pre-flight + cache check for prior snapshot. Load approval history for category urgency penalties. See references/memory-integration.md.
-
Phase 1: Parallel discovery via
audit-deep,ecosystem-health,repo-state-snapshot. Collect code markers and git history. Abort if not in a git repo. -
Phase 2: Normalize findings, assign
value_score(1–5), compute ROI:(severity × urgency × value_score) / effort. Dedup against open issues. Group into 3–6 themed bundles. See references/workflow.md § Ranking. -
Phase 3: Interactive propose gate. Display findings by theme with
Valcolumn and justification. Support--budget 2dgreedy knapsack. No GitHub writes before approval. See references/workflow.md § Propose. -
Phase 4: Generate specs for approved features only (via
adt-specs-spec-new). Skip if no features approved. -
Phase 5: Write
.claude/backlog/<YYYY-MM-DD>.mdplan file with phased task list grouped by severity.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/config-schema.md 2.0 KB
- references/critic-prompt.md 2.0 KB
- references/memory-integration.md 5.8 KB
- references/output-patterns.md 3.6 KB
- references/stop-conditions.md 2.9 KB
- references/workflow.md 15 KB
- scripts/board.sh 5.9 KB runs code
- scripts/dedup.sh 2.6 KB runs code
- scripts/discover.sh 2.9 KB runs code
- templates/issue-body.md 485 B
- templates/plan-header.md 797 B
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.
- 2d ago First seen · 126 lines · 62 tokens per session scan A f976448cf8e7
backlog is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,341 once invoked, about $0.0003 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
prpm-development
Use when developing PRPM (Prompt Package Manager) - comprehensive knowledge base covering architecture, format conversion, package types, collections, quality standards, testing, and deployment.
creating-cursor-rules-skill
Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-opencode-plugins
Use when creating OpenCode plugins that hook into command, file, LSP, message, permission, server, session, todo, tool, or TUI events - provides plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript event-driven modules.
creating-kiro-packages
Use when creating Kiro steering files or hooks - provides inclusion modes (always/fileMatch/manual), foundational files (product.md/tech.md/structure.md), and JSON hook configuration with event triggers.
creating-continue-packages
Use when creating Continue rules - provides required name field, alwaysApply semantics, glob/regex patterns, and markdown format with optional frontmatter.
thoroughness
Use when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis, implementation, and verification phases.