Borrowing it
Nothing to install: this file belongs to hadriansecurity/OpenHack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hadriansecurity/OpenHack/main/AGENTS.mdgit clone --depth 1 https://github.com/hadriansecurity/OpenHackWrote 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/instructions/hadriansecurity/openhack/agents-md)<a href="https://agentmods.dev/instructions/hadriansecurity/openhack/agents-md"><img src="https://agentmods.dev/badge/instructions/hadriansecurity/openhack/agents-md/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/instructions/hadriansecurity/openhack/agents-md"><img src="https://agentmods.dev/badge/instructions/hadriansecurity/openhack/agents-md.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.02001 | $0.02001 |
| Opus 5.5 | $0.00800 | $0.00800 |
| Sonnet 5.5 | $0.00400 | $0.00400 |
| Haiku 4.5 | $0.00200 | $0.00200 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repository is a file-based openhack workspace. When a human asks to start, initiate, run, resume, or continue a pentest/security review, use the tool structure before doing vulnerability analysis.
Required Pentest Flow
Do not begin with a broad LLM source sweep, direct expert pass, or ad hoc manual review of the target repository.
For a new target, use phase checkpoints:
- Run
openhack init-run <target> <git-url> [--run-id <run-id>] [--branch <branch>]. - Summarize the created run and source commit, then ask the human what
security experts to use before recon. Show every configured expert and the
option
all agents. - Run
openhack run-recon <target> <run-id> --all-agentsonly after approval, or run it with one or more--expert <expert-id>options if the human selected a subset. - Summarize recon counts and artifacts; ask whether to proceed to scenario
routing and backlog generation. If the human wants deeper source-pattern
coverage, rerun recon with
--semgrepbefore scenario routing. Recon writesrouting-units.jsonl; treat those clustered units as the primary router input instead of asking the router to reason over the full raw inventory dump. - After approval, run
openhack create-scenarios <target> <run-id>, have the scenario-router answer the rendered prompt, and record that router output withopenhack record-scenario-backlog <target> <run-id> router-result.jsonwithout inserting another human confirmation between prompt creation and backlog recording. The scenario-router must use the expert scope recorded before recon; do not create scenarios for unselected experts. The router must route from mandatoryrouting_unit_id + expertpairs when routing units are present, and use path/expert coverage requirements as a compatibility backstop. - Summarize backlog size and coverage notes; ask for one approval to run the entire unfinished scenario backlog. Batch approval is not batch analysis: every scenario still needs its own rendered prompt, source review, evidence, and result.
- Review only recorded
runs/<target>/<run-id>/scenarios/backlog/S*.mdexpert prompts and record results withopenhack record-scenario-result <target> <run-id> .... This records finished scenario results andfinding-candidates/; it does not create finalfindings/. - Summarize finding-candidate count and ask once to run the entire unfinished
finding triage backlog. Every candidate must use its own rendered
runs/<target>/<run-id>/finding-triage/prompts/S###-F###.mdprompt and its own finding-triage subagent. Render prompts withopenhack render-finding-triage-prompt <target> <run-id> <candidate-id>. - Record each finding-triage agent answer with
openhack record-finding-triage <target> <run-id> <candidate-id> triage-result.json. Onlyacceptedanddowngradedtriage decisions may materialize finalfindings/. - Validate with
openhack validate-run <target> <run-id>.
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 · 150 lines · 2,001 tokens per session scan A 273a706fc0ba
OpenHack AGENTS.md is an instructions file published in the GitHub repository hadriansecurity/OpenHack (747 stars, last pushed 4mo ago), licensed MIT. It adds 2,001 tokens to every session, about $0.0080 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.