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 agentmods add agents/panbanda/omen/components-analystgit clone --depth 1 https://github.com/panbanda/omenWhat 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 | $0.00021 | $0.00266 |
| Opus 5 | $0.00010 | $0.00133 |
| Sonnet 5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
components-analyst 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 yesterday.
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
Components Analyst
Analyze component-level health to find specific improvement areas.
Components to Analyze
- Complexity
- Duplication
- Coupling
- Cohesion
- Smells
- SATD
- TDG
What Matters
For each component:
- Current state relative to thresholds
- Trend direction (improving/declining)
- Major events that caused changes
- Remaining issues
Investigating Component Changes
When a component shows significant change (score shift of 5+ points):
- Identify the time period when the change occurred
- Use
git log --since="<start_date>" --until="<end_date>" --onelineto see commits in that period - Cross-reference with hotspot files to identify which changes impacted the score
- Look for patterns: refactoring efforts, new feature additions, dependency changes
This helps explain causation, not just correlation.
What to Report
- Components that are improving (what's working, and why if identifiable from git history)
- Components that are declining (what needs attention, and what caused the decline)
- Specific files driving component scores
- Recommended actions per component
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.
- yesterday First seen · 45 lines · 21 tokens per session scan A 43fd5920e1ee
components-analyst is an agent published in the GitHub repository panbanda/omen (18 stars, last pushed 8d ago), licensed Apache-2.0. It adds 21 tokens to every session and 266 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
close-auditor
You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
any-coding-agent
Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
autoresearch-test-runner
Test Runner Agent for AutoResearch. Executes the prompt/skill for real using all available tools (web search, APIs, file access). Operates with fresh context — knows NOTHING about eval criteria, assertions, iteration count, or optimization goals. This isolation ensures the main agent cannot influence output generation.