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/gopherguides/hype/agents-mdgit clone --depth 1 https://github.com/gopherguides/hypeWhat 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.00552 | $0.00552 |
| Opus 5 | $0.00276 | $0.00276 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
hype 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Core packages live at repo root (e.g., element.go, parser.go) and follow Go's standard package-per-file pattern, each paired with *_test.go. The CLI wrapper sits in cmd/hype, which builds the hype binary. Content templates and examples live under docs/, mdx/, and slides/, while reusable fixtures are stored in testdata/. Helper utilities and adapters reside in internal/ plus feature-specific subfolders such as atomx/ and binding/.
Build, Test, and Development Commands
make test: runsgo test -count 1 -race -vet=off -coveracross all packages except generated docs.make build: produces a localhypebinary fromcmd/hype/.go run ./cmd/hype --help: inspect CLI options without installing.make docsormake hype: regenerateREADME.mdfromhype.md; run after changing documentation templates.go install ./cmd/hype: install the CLI into your$GOBINfor reuse in other projects.
Coding Style & Naming Conventions
Use Go 1.25+ features conservatively and keep compiler warnings at zero. Format code via gofmt (tabs for indentation, blank lines between logical sections) and lint with revive using revive.toml. Exported identifiers should read like Parser, ExecuteError, while private helpers stay lowerCamel. Keep package boundaries focused; avoid cyclic imports by adding shared helpers to internal/.
Testing Guidelines
Unit tests mirror their source files (e.g., figure_test.go) and should cover happy paths plus failure parsing cases. Add integration coverage for the CLI in cli_integration_test.go when touching command behavior. Run make cov to inspect HTML coverage locally and target meaningful assertions rather than snapshot dumps. Table-driven tests are preferred; name cases with short strings describing the scenario. All new features require a failing test before implementation when practical.
Commit & Pull Request Guidelines
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 First seen · 26 lines · 552 tokens per session scan A 96bd0ed261ae
hype AGENTS.md is an instructions file published in the GitHub repository gopherguides/hype (56 stars, last pushed 5mo ago), licensed MIT. It adds 552 tokens to every session, about $0.0028 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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.