Borrowing it
Nothing to install: this file belongs to gohypergiant/agent-skills. 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/gohypergiant/agent-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/gohypergiant/agent-skillsWrote 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/gohypergiant/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/gohypergiant/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/gohypergiant/agent-skills/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.02152 | $0.02152 |
| Opus 5 | $0.01076 | $0.01076 |
| Sonnet 5 | $0.00430 | $0.00430 |
| Haiku 4.5 | $0.00215 | $0.00215 |
Grade A, and why
agent-skills 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 2d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file defines repository-specific agent behavior. Keep it limited to durable, non-obvious instructions that materially affect agent behavior. Do not use this file as a general project handbook. Link to canonical docs for project facts, architecture, onboarding, and other reference material. If a rule must hold with zero exceptions, enforce it in CI, hooks, scripts, permissions, or other deterministic controls.
Maintenance guidance
- Add instructions only when they prevent repeated mistakes, resolve real ambiguity, or capture durable repository behavior.
- Remove or rewrite rules that become stale, noisy, redundant, or ignored.
- Keep this file behavior-focused; move project facts, architecture, and handbook material to canonical companion documents.
- Prefer concrete, verifiable instructions over aspirational slogans.
What to optimize for
- Work primarily on creating, auditing, refining, and documenting reusable agent skills and their supporting guidance.
- Prioritize simplicity, consistency, and behavior preservation for skill and prompt edits.
- Prefer small, scoped changes over broad or speculative refactors across skills, docs, scripts, and supporting guidance.
- Make work traceable: state what was checked, changed, and verified.
- Follow repository-specific workflows and commands instead of guessing.
- Stay aligned with established repository patterns unless a change is explicitly approved.
How to communicate
- Use an adaptive style: concise by default, with more detail for audits, structural changes, and behavior-sensitive prompt work.
- For changes, report what changed, why, validation performed, and remaining uncertainty, TODOs, or follow-up suggestions.
- Ask before proceeding when information is missing or unclear.
- Do not speculate about code, files, or behavior that has not been inspected.
How to work
Before making changes
- Read the relevant skills, documentation, scripts, and nearby agent-facing guidance before editing.
- For behavior-defining artifacts, inspect neighboring behavior-bearing files and references before changing wording, structure, or examples.
- State the risk before making an edit that could change trigger coverage, workflow order, guardrail strength, or exact technical meaning.
- Update canonical skill content in
skills/first. Treat.agents/skills/only as a symlinked exposure layer. - Keep scope tight unless a broader change is explicitly approved.
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.
- 2d ago Changed · -50 lines · -363 tokens per session 520a844bef98
- 3d ago Changed · +87 lines · +574 tokens per session b1dbab32369a
- 7d ago First seen · 167 lines · 1,941 tokens per session scan A 457ba63d5ab9
agent-skills AGENTS.md is an instructions file published in the GitHub repository gohypergiant/agent-skills (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,152 tokens to every session, about $0.0108 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
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).
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.
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 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).
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.