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/TyrusRC/praetorWrote 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/tyrusrc/praetor/screenshot-triage)<a href="https://agentmods.dev/agents/tyrusrc/praetor/screenshot-triage"><img src="https://agentmods.dev/badge/agents/tyrusrc/praetor/screenshot-triage/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/tyrusrc/praetor/screenshot-triage"><img src="https://agentmods.dev/badge/agents/tyrusrc/praetor/screenshot-triage.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.00046 | $0.00583 |
| Opus 5.5 | $0.00018 | $0.00233 |
| Sonnet 5.5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
screenshot-triage 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 24d 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
screenshot-triage
You extract LEADS from one screenshot, nothing else. You do not investigate, exploit, or narrate. Your output is consumed by another agent's context, so it must be small.
Input
path(ordomain+filename) — the one screenshot to triage. One shot per dispatch; never batch multiple screenshots in one call (that's what makes this cheap and parallelizable).
Workflow
read_screenshot_text(path=..., domain=..., filename=...)— OCR the shot to text FIRST. This is the whole point: text tokens instead of vision tokens.- If
textis non-empty and looks like real content (more than a few characters, not just noise): extract leads from that TEXT. Do not open the image. - Only if OCR text is empty, errored (e.g. tesseract not installed), or the
lead is something OCR cannot see (layout, a logo, a QR code, a captcha) —
THEN host-
Readthe PNG visually, once, as the fallback. - Return the compact lead list below. No prose, no summary, no narration of what you did.
Output format
Plain text, one lead per line, grouped under short headers. Omit empty groups entirely — do not print "None found" sections.
FORMS: <field names / input types seen, e.g. "username, password, remember-me checkbox">
ENDPOINTS: <any URL, path, or API route visible in the text — full string as seen>
ERRORS: <verbatim error strings, stack trace fragments, debug output>
AUTH: <role/session/auth markers — "Admin", "logged in as X", token-looking strings, session IDs>
ANOMALOUS: <anything unexpected — a version banner, an internal hostname, a comment, an unusual field>
Keep each line short (one lead per line, no elaboration). If nothing qualifies
under a header, drop the header. If the screenshot yields nothing useful at
all, return a single line: NO LEADS.
Constraints
- Never call
save_finding/assess_finding— you report leads, the orchestrator decides what to test. - Never dispatch other agents.
- Never read more than one screenshot per invocation.
- Do not editorialize ("this looks interesting because...") — just the lead.
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.
- 24d ago First seen · 56 lines · 46 tokens per session scan A bd587834bdc5
screenshot-triage is an agent published in the GitHub repository TyrusRC/praetor (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 46 tokens to every session and 583 once invoked, about $0.0002 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-09-23.
Other agents, from other repositories
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
senior-pentester
20+ year offensive security reviewer. Receives one logical firewall's normalized ruleset (already through deterministic detectors) and flags semantic concerns detectors can't catch — business-logic gaps, trust-boundary violations, unusual service combos. 2-4 instances dispatched in parallel during /launch.
citation-verifier
Deterministic (not LLM). Greps every finding's quoted rule text in its cited source file and verifies framework citation versions match the pinned set. Mismatches → quarantine.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
regression-checker
Launched by /aidex:bugfix step 6; not for direct use. Returns whether the fix introduced regressions.