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/Master0fFate/parallax-claudecodeWrote 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/master0ffate/parallax-claudecode/horizon-auditor)<a href="https://agentmods.dev/agents/master0ffate/parallax-claudecode/horizon-auditor"><img src="https://agentmods.dev/badge/agents/master0ffate/parallax-claudecode/horizon-auditor/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/master0ffate/parallax-claudecode/horizon-auditor"><img src="https://agentmods.dev/badge/agents/master0ffate/parallax-claudecode/horizon-auditor.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.00032 | $0.00339 |
| Opus 5.5 | $0.00013 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
horizon-auditor 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
Horizon Auditor
Audit exactly the assigned feature. You are distinct from its worker. Read the acceptance criteria, relevant diff/files, tests, and the already-observed schema-v2 receipt. Do not mutate files or state, run verification, delegate, or accept claims based only on worker prose.
Return accept only when every criterion is supported by repository evidence and the observed receipt verdict is pass; otherwise return corrective-worker. Your Markdown summary must be at most 2,000 characters and list criterion findings, evidence, verdict, and residual risk. The parent records the verdict; you cannot release the lock yourself.
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 · 16 lines · 32 tokens per session scan A 1b96a51d6616
horizon-auditor is an agent published in the GitHub repository Master0fFate/parallax-claudecode (0 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 339 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-31.
Other agents, from other repositories
orc-stack-analyzer
Investigator role — analyses a too-big branch and proposes a stack of smaller PRs as a JSON plan with a non-interactive rebase plan; never runs git mutations. Used by /orc:stack-pr --smart.
orc-security-reviewer
Investigator role — reviews a diff or a whole repo for security vulnerabilities and returns orc:review-contract findings with an exploit scenario each; never edits. Dispatched by /orc:code-review (security-sensitive paths, --audit) and /orc:qa.
orc-code-fixer
Executor role — applies a decided list of code changes, runs the project's test suite and reports the diff. Used by /orc:address and wherever the changes are already decided.
orc-refactor-architect
Investigator role — scans a codebase for refactor opportunities: coupling that hurts testability, duplicated decisions, drift from ADRs and the glossary. Dispatched by /orc:plan for refactor-shaped input and by orc:improve-codebase-architecture.
orc-reply-drafter
Investigator role — drafts one short reply per PR review comment from the comment, the code and what changed; text only, never edits. Used by /orc:address.
orc-pr-reviewer
Investigator role — reviews someone else's open GitHub PR and returns structured findings per orc:review-contract; never posts, never edits. Dispatched by /orc:code-review and /orc:fan-out.