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.
git clone --depth 1 https://github.com/TakashiKakizoe1109/cc-backlog-connectWrote 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/plugins/takashikakizoe1109/cc-backlog-connect/plugin)<a href="https://agentmods.dev/plugins/takashikakizoe1109/cc-backlog-connect/plugin"><img src="https://agentmods.dev/badge/plugins/takashikakizoe1109/cc-backlog-connect/plugin/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/plugins/takashikakizoe1109/cc-backlog-connect/plugin"><img src="https://agentmods.dev/badge/plugins/takashikakizoe1109/cc-backlog-connect/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cc-backlog-connect 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 16d 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
{
"name": "cc-backlog-connect",
"version": "0.5.0",
"description": "Sync Backlog issues to local docs for Claude Code context",
"author": {
"name": "Takashi Kakizoe"
},
"repository": "https://github.com/TakashiKakizoe1109/cc-backlog-connect",
"homepage": "https://github.com/TakashiKakizoe1109/cc-backlog-connect",
"license": "MIT",
"keywords": [
"backlog",
"nulab",
"issue-sync",
"claude-code"
]
}
What it installs
The manifest is a name and a version. 5 skills, 2 commands, 1 hook travel with it, and installing the plugin installs all of them — 978 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 16d ago Changed c6c1492c6448
- 1mo ago First seen · 19 lines scan A ecc6ab6a78dc
cc-backlog-connect is a plugin published in the GitHub repository TakashiKakizoe1109/cc-backlog-connect (2 stars, last pushed 17d 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
project-artifact
Generate and publish a project status artifact — an opinionated, tabbed status page (overview & success criteria, the workstream sequence, next steps, plus background / plan / risks & open questions / decisions-FAQ when they earn a tab) published via the built-in Artifact tool to a default-private claude.ai page the…
personal-corp-os
Personal Corp framework: run your business with AI agents through GitHub, department repos, safe public releases, Telegram, agent gateways, html-draft diagrams, and media/art-direction workflows.
produck-skills
Pull real in-context user feedback into your coding agent and ship aligned fixes. Bundles the produck MCP (searchfeedback, getfeedback), a feedback-to-fix guide skill, and the user-alignment PRD skill.
agents-virtuoso
19 agents, 3 pre-composed teams, 7 role skills, and agent workflow skills — delegation patterns, team library, team dispatcher, subagent-driven development, verification discipline, plus all specialist and role agents.
infoops
Codex and OpenClaw compatible InfoOps skill for turning workstream signals into structured operational awareness and action priorities.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.