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/nid-team)<a href="https://agentmods.dev/plugins/openshift-eng/ai-helpers/nid-team"><img src="https://agentmods.dev/badge/plugins/openshift-eng/ai-helpers/nid-team.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
nid-team 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": "nid-team",
"description": "NI&D team PR triage and review workflow tools",
"version": "0.1.3",
"author": {
"name": "github.com/openshift-eng"
}
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 39 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 · 9 lines scan A 258da2b351af
nid-team 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
review-suite
Independent plan and delivery reviews with evidence-based verdicts.
draft
Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.
lets
Development workflow with session management, code review, and task tracking.
pm
GitHub issue lifecycle: brainstorm design approaches, create structured issues for LLM agent teams, triage and recommend next issues, audit and clean up stale backlogs, and deep-validate individual issues against the codebase.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
stocktake
Count what a tracker board claims against what the codebase actually holds, card by card, and move each one to the column its evidence supports. Reads every comment and attached image and rebuilds the numbered requirement list from the ticket BEFORE opening any completion record or diff, because a diff read first…