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/terrylica/cc-skillsWrote 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/terrylica/cc-skills/gh-tools)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/gh-tools"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/gh-tools/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/terrylica/cc-skills/gh-tools"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/gh-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gh-tools 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": "gh-tools",
"description": "GitHub workflow automation: GFM link validation, WebFetch enforcement, issue management, fork intelligence",
"version": "34.1.0",
"source": "./plugins/gh-tools",
"category": "development",
"author": {
"name": "terrylica",
"url": "https://github.com/terrylica"
},
"keywords": [
"github",
"pull-request",
"gfm",
"link-validation",
"gh-cli",
"webfetch",
"enforcement"
],
"strict": false,
"requires": [
"chrome-profiles"
]
}What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 260 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#gh-tools 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 Changed 7756e52b5c66
- 2d ago Changed 2f09e1156c2a
- 3d ago Changed 0f4c650de8df
- 5d ago Changed 435712e6bb2e
- 6d ago Changed a9ed3faf6eae
- 8d ago Changed 1be47f2e1a53
- 13d ago Changed 4f14a51124c7
- 14d ago Changed b0fe27c335db
- 15d ago Changed e233782bce09
- 16d ago First seen · 24 lines scan A 1fa3f888b729
gh-tools is a plugin published in the GitHub repository terrylica/cc-skills (0 stars, last pushed today), 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-09-05.
Other plugins, from other repositories
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
hydra
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts.
ticket-triage
Backlog-drain loop: rank the open tickets, dispatch the genuinely startable ones in parallel (worktree-isolated, role-briefed, honest width), verify and merge each result, and re-triage on every completion until the queue is empty or everything left needs the user.