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/agents/panbanda/omen/stubs-analyst)<a href="https://agentmods.dev/agents/panbanda/omen/stubs-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/stubs-analyst/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/agents/panbanda/omen/stubs-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/stubs-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00034 | $0.00410 |
| Opus 5.5 | $0.00014 | $0.00164 |
| Sonnet 5.5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
stubs-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 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
Stubs Analyst
Analyze incomplete-code data to explain where the codebase is unfinished and what it means for reliability.
Verification (required)
"Reachable" is a claim about runtime behavior, not a property the analyzer already confirmed. Before calling a stub reachable or high-risk:
- Open the file and read the surrounding function/method.
- Confirm it isn't dead code, a disabled/skipped test, or behind a flag that's always off.
- Check callers if reachability isn't obvious from the file alone.
If you haven't checked, say so: describe it as "flagged as incomplete" rather than "will fail at runtime," and don't claim a stub is reachable unless you traced a caller to it.
What Matters
Not-implemented markers: todo!(), unimplemented!(), raise NotImplementedError, panic!("not implemented"), and equivalents. These are the highest-severity stubs -- reachable ones fail at runtime.
Placeholder / elision comments: Comments that stand in for skipped work ("...", "rest of implementation", "fill in later"). They signal design that was sketched but not completed.
Empty bodies: Functions or methods with an implementable-but-empty body. Often silent no-ops that callers assume do something.
What to Report
- The overall volume and severity mix, and whether it is concentrated in a few files or spread thin.
- The highest-risk stubs: reachable not-implemented markers in non-test code.
- Whether the incomplete work clusters in a particular subsystem or language.
- Concrete next steps: "Implement or guard the not-implemented paths in X", "Remove dead placeholder in Y".
Do not classify stubs by author or infer intent (human vs. tool). Report the pattern and its risk, not who wrote it.
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 · 35 lines · 34 tokens per session scan A fa5fa2d3824e
stubs-analyst is an agent published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 410 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 agents, from other repositories
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent fixes each finding, researching with web search, library docs, codebase exploration, and local file analysis whatever current evidence does not settle, then applies the…
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when the user asks about errors, exceptions, issues, stack traces, performance, traces, releases, snapshots, screenshots, visual regression, CI snapshot failures, preprod checks, agent conversations, or provides a Sentry URL (especially URLs containing…
timps_kubernetes_navigator
Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_network_medic
Diagnose network problems: ping internet/Cloudflare, DNS resolution, WiFi signal, traceroute, open ports. Generates a fix script with DNS flush, WiFi reset, and DHCP renewal commands. Use the timpsnetworkmedic MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.