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.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00169 |
| Sonnet 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 7d 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.
- 7d 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 15d ago), licensed MIT. It adds 32 tokens to every session and 339 once invoked, about $0.0002 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-31.
Other agents, from other repositories
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
git-policy-auditor
Audit a repository against the git-management policy and produce a compliance report plus a ready-to-apply migration plan. Read-only — it inspects and proposes, never mutates. Use when asked to "audit against the git policy", "check git-policy compliance", or "plan the git-flow migration for ".
review
Structured code review — diff analysis, readability, correctness, and security. Read-only.
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…
pr-reviewer
Read-only, separate-context general code reviewer. It reviews a changed diff for correctness, regressions, maintainability, test coverage, and API/contract hygiene, and emits categorized findings (Block / Risk / Nit) for the operator to act on. Use it when an atom changes code and you want a fresh review pass the…
refactor-executor
Craft refactor phase worker. Executes pre-scoped, behavior-preserving refactor specs as atomic commits. Never judges what to refactor. Spawned by the craft refactor phase — do not auto-select.