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/cboone/agent-harness-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/cboone/agent-harness-plugins/address-issue)<a href="https://agentmods.dev/plugins/cboone/agent-harness-plugins/address-issue"><img src="https://agentmods.dev/badge/plugins/cboone/agent-harness-plugins/address-issue/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/cboone/agent-harness-plugins/address-issue"><img src="https://agentmods.dev/badge/plugins/cboone/agent-harness-plugins/address-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
address-issue 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
{
"author": {
"name": "Christopher Boone"
},
"description": "Fetch a GitHub issue, plan the work, stop for approval, then execute changes and commit with issue references.",
"homepage": "https://github.com/cboone/agent-harness-plugins",
"keywords": ["gh", "github", "issues", "workflow"],
"license": "MIT",
"name": "address-issue",
"repository": "https://github.com/cboone/agent-harness-plugins",
"skills": "./skills",
"version": "1.3.1"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 49 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 11833cd82263
- 5d ago Changed 4800397e0cda
- 8d ago Changed 8135b046e861
- 15d ago Changed 60a50fcc3b14
- 26d ago Changed 75e532c45a49
- 1mo ago Changed 904c12e17984
- 1mo ago Changed 45be5b29d1df
- 1mo ago First seen · 14 lines scan A 9e3f7dca142c
address-issue is a plugin published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed yesterday), 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
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
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…
obsidian-tracker
Project tracking, task management with kanban boards, bug logging, decision records (ADR), session management, and engineering traceability via Obsidian. Auto-tracks sessions, actions, bugs, and commits via hooks.
csw
Ship a tracker ticket: dispatch it into a worktree, drive it to a pull request, merge it after review, and clean up after itself.
backlog-md-cli
Backlog.md Task Management - CLI-first workflow orchestration for Git-native project management with strict file naming enforcement.