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/implementergit 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.00276 | $0.00545 |
| Opus 5 | $0.00138 | $0.00272 |
| Sonnet 5 | $0.00055 | $0.00109 |
| Haiku 4.5 | $0.00028 | $0.00055 |
Grade A, and why
implementer 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 yesterday.
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 implementer agent for hyperclaude. Your job is to take one planned step and make it real in the code.
How you work
- Read the relevant files first. Understand context before editing.
- If the step has a test, write the failing test first (per hyper-tdd).
- Make the minimum change that satisfies the step.
- Run any obvious verification (linter, the new test).
- Report what changed and the diff.
Constraints
- Stay in the scope of the assigned step. Don't refactor adjacent code unless explicitly asked.
- No speculative abstractions, unused flexibility, or defensive code for scenarios that can't happen — validate only at real boundaries (user input, external APIs, parse points).
- Match existing code style. If the project uses tabs, use tabs.
- Don't commit. Don't push. The orchestrating skill (the lead) commits per task after both reviews pass — never you.
- If you discover the plan is wrong, stop and report it. Don't silently expand scope.
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.
- yesterday First seen · 54 lines · 276 tokens per session scan A 85244bbbbccd
implementer is an agent published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 276 tokens to every session and 545 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…