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 instructions/openhackai/openhack/agents-mdgit clone --depth 1 https://github.com/openhackai/OpenHackWhat 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.00218 | $0.00218 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
OpenHack AGENTS.md 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
OpenHack Scanner Guidance
Repository scope
- This is the public OpenHack repository. Keep it focused on the scanner/CLI and its interactive TUI.
- Do not add hosted-service implementations or private deployment artifacts here, including HTTP service wrappers, cloud task definitions, account identifiers, or service-specific Dockerfiles.
- The AI pentest HTTP service and its deployment configuration belong in the
separate sibling
../openhack_pentest_service/directory.
CLI contract
- Running
openhackwith no flags always opens the interactive OpenHack security agent. - All other CLI entry points and non-interactive behaviors use flags on the
openhackcommand. - Do not introduce or recommend command-style subcommands such as
openhack doctororopenhack demo. Express proposed CLI functionality as flags, while functionality that belongs inside the interactive agent should remain part of that agent experience. - Tailor documentation, examples, product plans, tests, and user-facing copy to this contract.
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 · 24 lines · 218 tokens per session scan A c9cb51be92df
OpenHack AGENTS.md is an instructions file published in the GitHub repository openhackai/OpenHack (398 stars, last pushed 11d ago), licensed MIT. It adds 218 tokens to every session, about $0.0011 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-30.
Other instructions, from other repositories
strix AGENTS.md
Instructions for usestrix/strix, covering strix — agent guide, using strix from an agent and contributing to this repo.
prismor CLAUDE.md
Instructions for PrismorSec/prismor, covering prismor security — claude.md, prismor runtime protection, cloaking (secret prevention) and working in this repo.
tentaflake AGENTS.md
Instructions for timfewi/tentaflake, covering agent instructions — tentaflake, build & test, conventions, template rule and keep docs in sync.
aptl AGENTS.md
Instructions for Brad-Edwards/aptl, covering agent instructions, ground control context, skill installation, aces asset inventory capture skill and ground control overview.
prismor AGENTS.md
Instructions for PrismorSec/prismor, covering agents.md, primary objectives, start here, how to work in this repo and 1. treat security guidance as product logic.
aptl CLAUDE.md
Instructions for Brad-Edwards/aptl: DO NOT assume you can skip fixing pre-existing issues or bugs. If you see a problem, tell the user and ask if they want you to fix it.