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/dodobrands/ai-hubWrote 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/dodobrands/ai-hub/testops)<a href="https://agentmods.dev/plugins/dodobrands/ai-hub/testops"><img src="https://agentmods.dev/badge/plugins/dodobrands/ai-hub/testops/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/dodobrands/ai-hub/testops"><img src="https://agentmods.dev/badge/plugins/dodobrands/ai-hub/testops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
testops 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 1mo 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": "testops",
"version": "0.1.1",
"description": "Allure TestOps integration: test cases, launches, projects, defects, jobs, test plans",
"author": {
"name": "SOM Team"
}
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 28 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.
- 1mo ago First seen · 9 lines scan A e31b85f2c766
testops is a plugin published in the GitHub repository dodobrands/ai-hub (7 stars, last pushed 4d ago), 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-04.
Other plugins, from other repositories
rosetta-light
Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails. (lightweight: simpler workflows, smaller models).
sdlc-skills
Role-based agents and workflow skills for software delivery (BA, Tech Lead, PM, devs, QA, PA).
dxos
Durable, resumable project and task tracking for coding agents: a committed registry of work-streams plus a TASKS.md ledger per project, driven by one /dxos:project command. Adds /dxos:qa for running the executable QA tests and suites declared in .mdl specs, and bundles the DXOS Composer connector that serves the mcp.
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.
cantrips
The core engineering loop for coding agents (Claude Code, Codex CLI): grill, spec, tickets, implement with TDD at agreed seams, review, commit, plus a user-gated compound step that turns session learnings into durable project memory. Basic spells a caster always has prepared.
dev-workflow
Guided development workflow: task decomposition, planning, peer plan review, browser plan approval, implementation, tidy, check/test, rules and code review, one commit per build step, rule updates, retrospectives; mob mode for a junior navigator.