Borrowing it
Nothing to install: this file belongs to KeeghanM/humn. 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/KeeghanM/humn/main/AGENTS.mdgit clone --depth 1 https://github.com/KeeghanM/humnWrote 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/keeghanm/humn/agents-md)<a href="https://agentmods.dev/instructions/keeghanm/humn/agents-md"><img src="https://agentmods.dev/badge/instructions/keeghanm/humn/agents-md.svg" alt="Measured on agentmods" 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.01290 | $0.01290 |
| Opus 5 | $0.00645 | $0.00645 |
| Sonnet 5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
humn 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 6d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
This file defines how coding agents should work in this repository.
It does not define the coding standards themselves. Coding, testing, architecture, observability, security, and review standards live in coding-standards.md.
Agents must use this file to understand how to approach work, and must use coding-standards.md to understand what good code looks like.
Instruction precedence
Follow instructions in this order:
- The user's current task instructions
- The closest applicable
AGENTS.md - Requirements artefacts for the task, such as PRDs, issues, ADRs, specs, README files, and architecture notes
coding-standards.md- Existing code patterns
If instructions conflict, follow the higher-priority instruction and call out the conflict in the final response.
If existing code conflicts with coding-standards.md, apply the standards to new and modified code, but do not perform broad unrelated rewrites unless required by the task.
Start every task with discovery
Before planning or editing code, inspect the repo root and obvious requirements locations, including:
/docs- README files
coding-standards.md- architecture notes
- any file that defines scope, behaviours, constraints, or review expectations
Use these artefacts as the source of truth for scope and implementation choices.
If the relevant requirements are unclear or missing, make a best-effort plan from the available evidence and call out the gap.
Required standards
Before editing code, locate and read coding-standards.md.
The standards file is authoritative for:
- TypeScript
- React
- Python
- testing
- architecture
- validation
- observability
- security
- infrastructure
- code review expectations
- commit message format
Do not duplicate or reinterpret these standards unless a task-specific requirement overrides them.
Delivery model
Default to single-PR delivery.
When asked to plan or implement, optimise for one comprehensive pull request that solves the real problem end to end.
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.
- 6d ago First seen · 192 lines · 1,290 tokens per session scan A cdd83426f275
humn AGENTS.md is an instructions file published in the GitHub repository KeeghanM/humn (8 stars, last pushed 2mo ago), licensed MIT. It adds 1,290 tokens to every session, about $0.0064 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.