Borrowing it
Nothing to install: this file belongs to justguy/hoplon. 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/justguy/hoplon/main/AGENTS.mdgit clone --depth 1 https://github.com/justguy/hoplonWrote 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/justguy/hoplon/agents-md)<a href="https://agentmods.dev/instructions/justguy/hoplon/agents-md"><img src="https://agentmods.dev/badge/instructions/justguy/hoplon/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/justguy/hoplon/agents-md"><img src="https://agentmods.dev/badge/instructions/justguy/hoplon/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.00512 | $0.00512 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
hoplon 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
These instructions apply to the entire repository.
Start here
Read:
README.mdHOPLON_VISION.mdARCHITECTURE.mdCONTRIBUTING.md
Working method
Use TRACE -> REPORT -> FIX -> PROVE:
- Trace the complete data path and identify the writer, consumer, enforcement point, and lifecycle of every changed contract.
- Report the observed behavior and the weakest link before changing code.
- Fix the smallest complete slice; do not add parallel mechanisms.
- Prove the claimed behavior through a real operation, session, handler, or transport path.
Architecture rules
- Environment access belongs behind injected adapters.
- Hoplon never owns model selection, retry, escalation, or approval policy.
- Deterministic
PASS/BLOCKauthority uses manifest, path, snapshot, and AST facts only. - Advisory providers must report unavailable or degraded states honestly and cannot silently change deterministic verdicts.
- Imports flow from engine and operations toward adapters/contracts/pure utilities, never toward a host orchestrator.
- Use named ES-module exports, strict TypeScript, and
async/await. - Keep every TypeScript file under
src/hoplonat or below 300 lines. - Do not truncate agent-facing evidence with arbitrary character caps.
- Avoid new defaults, thresholds, or blocking behavior unless the change is explicit, justified, documented, and supported by an adversarial corpus.
Tests
- Bug fixes require a regression test that reproduces the failure.
- Contract changes require producer and consumer coverage.
- Runtime claims require a real handler, dispatch, session, or flow test.
- Prefer the narrow Vitest file or directory that owns the changed surface.
- Run
npm run test:archfor architecture changes andnpm run test:prooffor deterministic kernel changes. - Tests must inject filesystem, versioning, snapshot, lock, provider, and behavior-runner dependencies rather than relying on ambient services.
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.
- 2mo ago First seen · 60 lines · 512 tokens per session scan A 29763b8109cc
hoplon AGENTS.md is an instructions file published in the GitHub repository justguy/hoplon (0 stars, last pushed 2mo ago), licensed MIT. It adds 512 tokens to every session, about $0.0020 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 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.