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/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/node-bug)<a href="https://agentmods.dev/plugins/openshift-eng/ai-helpers/node-bug"><img src="https://agentmods.dev/badge/plugins/openshift-eng/ai-helpers/node-bug.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
node-bug 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": "node-bug",
"description": "Node-specific bug triage, sub-team routing, and assignment suggestions for OpenShift Node team components",
"version": "0.0.2",
"author": {
"name": "github.com/openshift-eng"
},
"dependencies": [
{
"name": "node-team",
"version": "^1.0.0"
}
]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 21 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.
- 2d ago First seen · 15 lines scan A 699ad1e00993
node-bug is a plugin published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 2d ago), 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-09-05.
Other plugins, from other repositories
datadog
Access Datadog logs, metrics, monitors, dashboards, SLOs, events, traces, and incidents.
agent-alchemy-dev-tools
Agent Alchemy Dev Tools — dev utilities, debugging, and workflow enhancements.
incident-response
Production incident management, triage workflows, and automated incident resolution.
apple-craft
A collection of skills for Apple-platform development, including implementation, debugging, code review, long-running projects, App Store delivery, Xcode integration, and Pencil design work. Xcode is Apple's tool for building its apps, and the App Store is Apple's software marketplace.
debugging
Systematic debugging skills: root cause tracing, defense-in-depth validation, verification before completion.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.