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/flags-analyst)<a href="https://agentmods.dev/agents/panbanda/omen/flags-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/flags-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/flags-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/flags-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.00017 | $0.00249 |
| Opus 5.5 | $0.00007 | $0.00100 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
flags-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
Flags Analyst
Analyze feature flag data to find cleanup opportunities.
Verification (required)
"Security-sensitive code" is your inference from a flag's name or file path, not a fact the analyzer gives you. Before calling a flag high-risk on that basis, open the files that reference it and confirm what they actually do. If you haven't checked, describe the flag's age and reference count without asserting what the guarded code does.
What Matters
Age = risk:
- < 30 days: Active, normal
- 30-90 days: Review rollout status
- 90-180 days: Stale, cleanup candidate
- 180+ days: Debt, priority cleanup
- 2+ years: Remove immediately
Context matters:
- Flags in auth/payment code = higher risk if stale
- Flags referenced in 10+ files = harder to remove, do it sooner
What to Report
- Oldest flags and why they should be removed
- Flags in security-sensitive code
- Flags with high reference counts (cleanup complexity)
- Specific verification steps before removal
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 · 33 lines · 17 tokens per session scan A c9a8f9c3cba9
flags-analyst is an agent published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 249 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
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
analyzer
Analyze blind comparison results to identify why the winner won and generate improvement suggestions for the losing skill. Also surfaces patterns in benchmark runs.
agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
dangerous-agent
An agent with security issues for testing.
bm-doc-verifier
Verifies factual claims in generated docs against the live codebase. Returns structured JSON per doc.
Demonstrate
Agent for demonstrating VS Code features.