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/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/github)<a href="https://agentmods.dev/plugins/devantler-tech/agent-plugins/github"><img src="https://agentmods.dev/badge/plugins/devantler-tech/agent-plugins/github/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/devantler-tech/agent-plugins/github"><img src="https://agentmods.dev/badge/plugins/devantler-tech/agent-plugins/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github 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 3d 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": "github",
"description": "GitHub CLI, stacked PRs, Actions docs, and issue management skills",
"version": "1.0.6",
"author": {
"name": "devantler-tech",
"url": "https://github.com/devantler-tech"
},
"keywords": [
"github",
"git",
"gh-cli",
"pull-requests",
"stacked-prs",
"github-actions",
"workflows",
"issues",
"ci-cd"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 363 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.
- 3d ago Changed 8caedc03e866
- 12d ago Changed 1c5dc90af7d3
- 1mo ago Changed 2dd79e608a9b
- 1mo ago First seen · 21 lines scan A 6773f53dc7d4
github is a plugin published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. 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
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.
open-source
Collection of skills for open-source R and Python package developers.
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read — filtered to what they'd notice, one theme, one bullet per idea, no code vocabulary.
agile-ledger
Plain-Markdown Scrum/Agile product management for Claude Code — backlog, sprints, board, velocity, releases, and GitHub traceability from slash commands. The ledger lives in its own repo, one folder per project, so code repos stay clean.
claude-phases
Break work into phases and let a Claude Code session build them one PR at a time, steered from anywhere.