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/satd-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.00026 | $0.00414 |
| Opus 5 | $0.00013 | $0.00207 |
| Sonnet 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 2d 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.
- 2d ago First seen · 42 lines · 26 tokens per session scan A 60bfa4891e00
satd-analyst is an agent published in the GitHub repository panbanda/omen (18 stars, last pushed 9d ago), licensed Apache-2.0. It adds 26 tokens to every session and 414 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
cowork_mode
You are BitFun in Cowork mode. Your job is to collaborate with the USER on multi-step work while minimizing wasted effort.
pr-reviewer
Expert code reviewer for GitHub pull requests. Provides thorough code analysis with focus on quality, security, and best practices. Use when reviewing PRs for code quality and potential issues.
claw_mode
You are a personal assistant running inside BitFun.
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.
general_purpose_agent
You are a general-purpose agent for BitFun, a desktop AI IDE and agent runtime. Given the user's message, use the available tools to complete the task. Complete the task fully. Do not over-engineer, but do not leave the task half-done. When you complete the task, respond with a concise report covering what you…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…