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/kolodkin/devpowersWrote 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/kolodkin/devpowers/devpowers)<a href="https://agentmods.dev/plugins/kolodkin/devpowers/devpowers"><img src="https://agentmods.dev/badge/plugins/kolodkin/devpowers/devpowers/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/kolodkin/devpowers/devpowers"><img src="https://agentmods.dev/badge/plugins/kolodkin/devpowers/devpowers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
devpowers 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.
What it actually says
{
"name": "devpowers",
"description": "Developer productivity skills: GitHub Actions runner and checker, PR/CI status checker, Jira setup and ticket creator, git commit helper, markdown shortener, local/remote Docker debuggers, MCP server setup, an e2e UI screenshot report generator, and a bottom-line output style for terse chat replies.",
"version": "1.12.0",
"author": {
"name": "kolodkin"
},
"homepage": "https://github.com/kolodkin/devpowers",
"keywords": ["git", "commit", "github", "actions", "workflow", "ci", "pr", "pull-request", "review", "skill", "install", "markdown", "docs", "shortify", "docker", "ssh", "debug", "logs", "mcp", "setup", "e2e", "screenshots", "playwright", "report", "jira", "atlassian", "ticket", "issue", "output-style", "concise", "terse"]
}
What it installs
The manifest is a name and a version. 12 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 1,069 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill jira-ticket A 187 tokens
- Skill action-run A 74 tokens
- Skill action-check A 76 tokens
- Skill jira-setup A 142 tokens
- Skill setup-mcp A 108 tokens
- Skill screenshots A 63 tokens
- Skill shortify A 75 tokens
- Skill git-commit A 52 tokens
- Skill local-docker-debug A 68 tokens
- Skill check-pr B 112 tokens
- Skill ssh-docker-debug B 75 tokens
- Skill brainstorming A 37 tokens
- MCP server github A not measured
What ships with it
1 file beside plugin.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.
- 2d ago Changed e82857bfd441
- 16d ago Changed 7f5d80ee7028
- 1mo ago First seen · 11 lines scan A dc7655fec2bf
devpowers is a plugin published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d 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
github
GitHub Actions, Workflows, act local testing, community health files, Dependabot consolidation, and PR review.
merge-pr
Merge PRs matching repo history conventions. Includes readiness checks, CI watching, stack detection, and automated rebasing.
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
charon
Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.
forgedock
Autonomous AI development pipeline that uses GitHub as a structured knowledge graph for Claude Code agents. Adds /work-on, /review-pr, /quality-gate, /orchestrate, and 20+ pipeline commands.