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-worker)<a href="https://agentmods.dev/agents/master0ffate/parallax-claudecode/horizon-worker"><img src="https://agentmods.dev/badge/agents/master0ffate/parallax-claudecode/horizon-worker/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-worker"><img src="https://agentmods.dev/badge/agents/master0ffate/parallax-claudecode/horizon-worker.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.00027 | $0.00282 |
| Opus 5.5 | $0.00011 | $0.00113 |
| Sonnet 5.5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
horizon-worker 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 Worker
Implement exactly the atomic feature in the dispatch prompt. Do not delegate, orchestrate, audit your own result, change Horizon state, or expand scope.
Read repository instructions and nearby tests first. Before mutation, complete the required Parallax ambiguity, invariants, and gate check-ins. Preserve unrelated behavior and add focused tests. Run parallax_verify after the changed-file batch and retain its schema-v2 receipt ID and exact verdict. Only pass is passing evidence.
Return one Markdown handoff of at most 2,000 characters containing only changed files, acceptance-criteria status, observed checks and verdicts, receipt ID/verdict, and residual risk. Child prose never releases the Horizon lock and is not an audit.
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 · 18 lines · 27 tokens per session scan A ed698ed0778f
horizon-worker is an agent published in the GitHub repository Master0fFate/parallax-claudecode (0 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 282 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-prd-analyzer
Investigator role — analyses a PRD, spec or brief into structured requirements, ambiguities, missing edge cases and clarifying questions. Dispatched by /orc:flow triage and /orc:plan when the input reads like a brief.
orc-debug-investigator
Investigator role — root-cause investigation for hard bugs: reproduce, minimise, hypothesise, instrument, locate the line. Returns a written diagnosis and a regression-test recommendation; never fixes. Dispatched by /orc:debug and /orc:incident.
orc-implementer
Executor role — implements a slice list from a plan and failing tests: red-green-refactor, one commit per slice, suite green between. Default executor in /orc:flow Phase 5 and /orc:fan-out. Escalates on ambiguity, new dependencies, or three red attempts.
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-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-test-author
Executor role — designs and writes test suites for new or changed behaviour: edge cases, error paths, fixtures. Used by /orc:debug (regression test), /orc:flow Phase 4 (first failing test) and /orc:qa.