Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Abilityai/abilities/plugin install agent-devWrote 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/abilityai/abilities/add-backlog)<a href="https://agentmods.dev/skills/abilityai/abilities/add-backlog"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/add-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/abilityai/abilities/add-backlog"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/add-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.00043 | $0.02454 |
| Opus 5.5 | $0.00017 | $0.00982 |
| Sonnet 5.5 | $0.00009 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade D, and why
install-github-backlog scanned grade D with 2 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ 2>/dev/null Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ".claude/skills/$s" && cp -R "$SRC" ".claude/skills/$s" How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install GitHub Backlog
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.install-github-backlog vX.Y — recent: <summary>. Then proceed.
Add GitHub Issues task management to any Claude Code agent. This wizard copies the plugin's standalone workflow skills into your agent's .claude/skills/ directory — the installed agent has no runtime plugin dependency, and the skills are the same files Trinity instances assign from the trinity-skills library.
What you get:
| Skill | Purpose |
|---|---|
/backlog |
Priority-ordered view of open issues |
/roadmap |
Strategic view grouped by skill area |
/groom |
Tag issues with skill:* labels, set priorities |
/claim |
Grab the next task, mark it in-progress |
/autoplan |
Analyze a skill issue before implementing |
/close |
Close an issue without a git commit |
/commit |
Stage skill file changes, commit, close issue |
/sprint |
Human-supervised develop cycle (one issue end-to-end) |
/work-loop |
Autonomous processing (schedulable on Trinity) |
The agent's repository becomes its task queue. Issues = work items. Skills = the units of work.
Process
Step 1: Verify Environment
git remote get-url origin 2>/dev/null
If not a git repo or no GitHub remote, stop and explain:
"This skill requires a GitHub repository. Initialize with git init and gh repo create."
Step 2: Verify gh CLI
gh auth status 2>&1 | head -3
If not authenticated, tell user to run ! gh auth login and re-run.
Step 3: Check for Existing Skills
ls .claude/skills/ 2>/dev/null
List which of the target skills already exist. If any do, ask:
- Overwrite — Replace with fresh versions
- Skip existing — Only create missing ones
- Cancel — Abort
Step 4: Ask Workflow Preferences
Use AskUserQuestion:
- Header: "Work Loop Schedule"
- Question: "How should the autonomous work-loop run?"
- Options:
- Daily at 9am (
0 9 * * *) — recommended - Every 4 hours (
0 */4 * * *) - Manual only (no schedule)
- Daily at 9am (
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 Changed · -515 lines scan B → D 6e5fc8634347
- 1mo ago First seen · 739 lines · 43 tokens per session scan B 99536275e52e
install-github-backlog is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 2,454 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…