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.
npx skills add panbanda/omen --skill audit-architecturegit 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/skills/panbanda/omen/audit-architecture)<a href="https://agentmods.dev/skills/panbanda/omen/audit-architecture"><img src="https://agentmods.dev/badge/skills/panbanda/omen/audit-architecture/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/skills/panbanda/omen/audit-architecture"><img src="https://agentmods.dev/badge/skills/panbanda/omen/audit-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00938 |
| Opus 5.5 | $0.00013 | $0.00375 |
| Sonnet 5.5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
audit-architecture 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Architecture
Analyze the structural health of a codebase by examining coupling, cohesion, hidden dependencies, and design patterns.
Prerequisites
Omen CLI must be installed and available in PATH.
Workflow
Step 1: Map Module Dependencies
Run the dependency graph analysis:
omen -f json graph
Look for:
- Circular dependencies
- God modules (too many dependents)
- Orphan modules (no connections)
Step 2: Detect Architectural Smells
Run the smells analysis:
omen -f json smells
Detects cyclic dependencies, hub modules, unstable dependencies, and central connectors using Tarjan's SCC algorithm.
Step 3: Measure Cohesion
Run the cohesion analysis for CK metrics:
omen -f json cohesion
Metrics to watch:
- LCOM (Lack of Cohesion): > 0.7 indicates class doing too many things
- WMC (Weighted Methods per Class): > 30 indicates too complex
- CBO (Coupling Between Objects): > 10 indicates too many dependencies
Step 4: Find Hidden Dependencies
Run the temporal coupling analysis:
omen -f json temporal
Files that always change together but don't have explicit imports indicate:
- Shared global state
- Implicit contracts
- Missing abstractions
Step 5: Check Ownership Distribution
Run the ownership analysis:
omen -f json ownership
Look for:
- Modules with no clear owner
- Over-concentrated ownership (bus factor = 1)
- Fragmented ownership (many contributors, none dominant)
Architecture Smells
Common issues to identify:
| Smell | Detection | Impact |
|---|---|---|
| Circular Dependency | A -> B -> C -> A in graph | Hard to test, modify |
| God Module | > 50% of code depends on it | Single point of failure |
| Shotgun Surgery | High temporal coupling | Changes ripple everywhere |
| Feature Envy | Low cohesion in classes | Wrong abstraction boundaries |
| Knowledge Silo | Bus factor = 1 | Team risk |
Output Format
Present architecture review as:
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 · 161 lines · 33 tokens per session scan A 1e7df9185b2c
audit-architecture is a skill published in the GitHub repository panbanda/omen (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 938 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other skills, from other repositories
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
find-simplifications
Use when asked to find or plan Cherry Studio cleanup, simplification, refactoring, dead-code removal, duplicated state removal, unnecessary APIs, speculative generality, or library replacements, especially when the result should become evidence-backed proposed Agent Notes.
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by OpenBitFun's unified Review mechanism instead.…