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 es6kr/skills --skill backloggit clone --depth 1 https://github.com/es6kr/skillsWrote 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/es6kr/skills/backlog)<a href="https://agentmods.dev/skills/es6kr/skills/backlog"><img src="https://agentmods.dev/badge/skills/es6kr/skills/backlog/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/es6kr/skills/backlog"><img src="https://agentmods.dev/badge/skills/es6kr/skills/backlog.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.00196 | $0.00830 |
| Opus 5.5 | $0.00078 | $0.00332 |
| Sonnet 5.5 | $0.00039 | $0.00166 |
| Haiku 4.5 | $0.00020 | $0.00083 |
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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog
Unified backlog lifecycle management and orchestration across multiple storage layers (session WIP, markdown checklist files, and issue trackers).
Overview
The backlog skill provides a consistent operational interface for capturing, classifying, synchronizing, prioritizing, and maintaining backlogs across software development lifecycles.
Incoming Task / Request
├─ In-Session Short-Lived ──→ /wip (Session Task API / TodoWrite)
├─ Workspace Markdown File ──→ /fix-plan (fix_plan.md / checklist.md)
└─ Team-Shared External ──→ Issue Tracker (GitHub Issues / Forge / Secondary Trackers)
Topics
| Topic | Description | Guide |
|---|---|---|
comment |
Post follow-up notes and nested review findings as comments on parent issues | comment.md |
create |
Create issues and intake items via API with fallback mechanisms | create.md |
prune |
Demote lower-priority items (P2/P3) and stale entries to preserve lean active focus sections | prune.md |
record |
Record this session's completed work + register next-session candidates (session/file/issue routing) | record.md |
Default Invocation (/backlog)
When invoked with no arguments, the backlog skill runs the standard health and synchronization pipeline:
- Sync: Poll external status for linked issues and pull requests to update resolved items.
- Priority Triage: Re-evaluate urgency and blockers across active items.
- Hygiene & Prune: Identify bloated or stale tasks exceeding active capacity.
- Summary Report: Output an actionable breakdown of immediate priority candidates.
Configuration
| Option | Default | Description |
|---|---|---|
--file=<path> |
fix_plan.md |
Target markdown checklist path for local operations |
--role=<pm|deep|impl> |
(unset) | Execution role profile filter for pipeline scoping |
--secondary-sync=<skill>:<topic> |
(unset) | Abstract receiver contract for non-GitHub backlog synchronization |
What ships with it
24 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.
- .clawhubignore 37 B
- CHANGELOG.md 6.2 KB
- comment.md 3.0 KB
- create.md 7.8 KB
- prune.md 5.1 KB
- record.md 9.9 KB
- scripts/intake.py 15 KB runs code
- scripts/plane_bulk_update.py 13 KB runs code
- scripts/plane_client.py 19 KB runs code
- scripts/plane_create_comment.py 7.3 KB runs code
- scripts/plane_create_entity.py 29 KB runs code
- scripts/plane_create_issue.py 28 KB runs code
- scripts/plane_indexify.py 11 KB runs code
- scripts/plane_sync.py 22 KB runs code
- scripts/plane_update_entity.py 16 KB runs code
- scripts/plane_verify_identifier.py 5.1 KB runs code
- scripts/prune_p2p3.py 12 KB runs code
- scripts/test_plane_client_browse_url.py 3.6 KB runs code
- scripts/test_plane_client_intake.py 4.9 KB runs code
- scripts/test_plane_create_issue_browse_url.py 5.7 KB runs code
- scripts/test_plane_intake_script.py 1.9 KB runs code
- scripts/test_plane_priority_mapping.py 6.3 KB runs code
- scripts/test_plane_sync.py 21 KB runs code
- scripts/test_plane_verify_identifier.py 6.3 KB runs code
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.
- yesterday Changed · +1 lines · +15 tokens per session da19d7a2e329
- 1mo ago First seen · 66 lines · 181 tokens per session scan A e84aec1545fb
backlog is a skill published in the GitHub repository es6kr/skills (2 stars, last pushed yesterday), licensed MIT. It adds 196 tokens to every session and 830 once invoked, about $0.0008 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…