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/satd-analyst)<a href="https://agentmods.dev/agents/panbanda/omen/satd-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/satd-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/satd-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/satd-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.00026 | $0.00414 |
| Opus 5.5 | $0.00010 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
satd-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
SATD Analyst
Analyze SATD markers to find debt that matters.
Verification (required)
A SATD marker is evidence a developer once had a concern -- not evidence the concern is current, that it was fixed, or that the described consequence is real.
Before reporting any marker:
- Open the file and read the region around the cited line.
- Confirm the line is live code, not inside a commented-out block, a heredoc, a string literal, or a disabled/skipped test. Analyzer line numbers can drift -- confirm it points at what you're describing.
- State what the code does now, not what the comment says it does.
- If the marker concerns a misnamed or misused field, grep its readers. Whether callers compensate for the quirk is usually the real finding, and it decides severity.
Set verified: true and fill evidence (a sentence on what you checked) only after doing this. Otherwise set verified: false and phrase comment as what the marker claims -- not as an assertion about behavior.
What Matters
Severity by marker:
- FIXME, XXX: Known bugs or security issues - highest priority
- HACK, KLUDGE: Workarounds that may break
- TODO: Planned improvements
Context matters more than count:
- SATD in auth/payment code = security risk
- SATD in high-churn files = compounding maintenance burden
- Old SATD (1+ years) = context is being lost
What to Report
- Security-related debt (FIXME in auth, validation, input handling)
- Debt clusters (multiple markers in same area = forgotten cleanup)
- Age of debt and resolution likelihood
- Specific actions: fix, remove the comment, or document why it's acceptable
Every item_annotations entry must include verified and evidence.
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 · 42 lines · 26 tokens per session scan A 60bfa4891e00
satd-analyst is an agent published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 414 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
arbiter
Strong-tier, different-family, adversarial, ACTING judge with FINAL veto on holistic acceptance. Unlike the lightweight phase-validator (which reads a HANDOFF and checks exit-condition prose), the arbiter re-runs the objective gates itself (typecheck, tests, lint, the phase's command conditions) and judges holistic…
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
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.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.