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.
/plugin marketplace add backloghq/backlognpx agentmods add plugins/backloghq/backlog/marketplacegit clone --depth 1 https://github.com/backloghq/backlogGrade A, and why
backloghq-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.
What it actually says
{
"name": "backloghq-backlog",
"owner": {
"name": "BacklogHQ",
"email": "[email protected]"
},
"metadata": {
"description": "Persistent task management for Claude Code and agent teams"
},
"plugins": [
{
"name": "backlog",
"source": "./",
"description": "Persistent, cross-session task management for Claude Code. Agent coordination, doc-driven development, exposed as MCP tools and skills.",
"version": "2.4.3",
"author": {
"name": "BacklogHQ"
},
"homepage": "https://backloghq.io",
"repository": "https://github.com/backloghq/backlog",
"license": "MIT",
"keywords": ["tasks", "planning", "backlog", "persistence", "agent-teams"],
"category": "productivity"
}
]
}
What ships with it
1 file beside marketplace.json 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.
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 First seen · 27 lines scan A 9c8d61c636f3
backloghq-backlog is a plugin published in the GitHub repository backloghq/backlog (5 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
ai-skills
Plugin marketplace listing 8 plugins: security-hooks, pr-review-triage, dev-skills, nix-skills, git-workflow.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.