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/panbanda/omenWrote 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/panbanda/omen/omen-development)<a href="https://agentmods.dev/plugins/panbanda/omen/omen-development"><img src="https://agentmods.dev/badge/plugins/panbanda/omen/omen-development/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/panbanda/omen/omen-development"><img src="https://agentmods.dev/badge/plugins/panbanda/omen/omen-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
omen-development 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": "omen-development",
"source": "./plugins/development",
"description": "Code analysis skills for active development: find bugs, assess impact, plan refactoring, audit architecture, and more"
}What it installs
The manifest is a name and a version. 13 skills travel with it, and installing the plugin installs all of them — 304 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill setup-config A 28 tokens
- Skill audit-architecture A 33 tokens
- Skill target-tests A 31 tokens
- Skill track-trends A 32 tokens
- Skill assess-impact A 35 tokens
- Skill audit-flags A 30 tokens
- Skill onboard-codebase A 35 tokens
- Skill report-debt A 32 tokens
- Skill plan-refactoring A 11 tokens
- Skill context A 10 tokens
- Skill focus-review A 10 tokens
- Skill find-bugs A 10 tokens
- Skill check-quality A 7 tokens
What ships with it
2 files beside marketplace.json#omen-development 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.
- 1mo ago First seen · 5 lines scan A 609a64dc5bc6
omen-development is a plugin published in the GitHub repository panbanda/omen (20 stars, last pushed today), 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-03.
Other plugins, from other repositories
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
synapse-mcp
A persistent code-knowledge graph for AI agents. Runs locally. Writes safely.
weavatrix
Evidence infrastructure for AI software agents: 67 read-only repository intelligence tools through MCP.
swe-skills
17 agent skills for engineering analysis and judgment — PR risk review, repo introspection, audits, ownership maps, refactor opportunities. See https://cdd.dev/skill/.
issue-review
A plugin for systematic software-problem diagnosis, coordinating five specialised agents for problem analysis, code investigation, root-cause finding, Git history analysis, and log analysis.
chrome-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.