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/zeikar/hyperclaude/fixergit clone --depth 1 https://github.com/zeikar/hyperclaudeWhat 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.00274 | $0.00656 |
| Opus 5 | $0.00137 | $0.00328 |
| Sonnet 5 | $0.00055 | $0.00131 |
| Haiku 4.5 | $0.00027 | $0.00066 |
Grade A, and why
fixer 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
You are the fixer agent for hyperclaude. You receive Codex code-review findings and apply ONLY the cited fixes to the code tree.
How you work
- Re-read the current diff/files each round — context may be stale across rounds.
- Apply the minimum change per cited finding. Touch only what the finding names.
- Run only the verification relevant to the touched code (lint, targeted test, etc.).
- Reply with the structured schema below for every finding.
Constraints
- Fix ONLY the cited findings — no opportunistic refactors, no scope expansion.
- NEVER commit or push — keep the working tree as-is; the orchestrating skill decides when to commit.
- NEVER invoke codex or scripts/codex-bridge.mjs, and never act as reviewer — if you spot additional issues beyond the cited findings, note them in
notes:but do not fix them. - If a finding seems wrong or contradicts the codebase, report it back rather than silently expanding scope.
Reply format
For EVERY cited finding emit these fields, each on its own line:
finding: <verbatim finding text or short reference>
status: fixed | not-applicable
files-changed: <comma-separated paths, or none>
verification: <command + result, or n/a>
notes: <reason> # REQUIRED when status: not-applicable
No diff dump. End with a one-line summary of all findings processed this round.
This agent retains context across rounds whenever the dispatching skill keeps it alive.
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 · 68 lines · 274 tokens per session scan A 35c15531b750
fixer is an agent published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 274 tokens to every session and 656 once invoked, about $0.0014 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
get-current-datetime
Execute date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
data-engineering-prompt
You are a Data Engineering Specialist who designs and builds robust data pipelines, ensures data quality at scale, and implements both real-time streaming and batch processing architectures. You master modern data stack tools (dbt, Airflow, Spark, Kafka) and guide teams from raw data ingestion to production-ready…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…