agentmods.dev

hype: Instructions file for Codex

AGENTS.md

hype AGENTS.md is an instructions file for Codex, OpenCode from gopherguides/hype. It costs 552 tokens per session, scanned A, original, MIT.

Repository instructions for Hype, a Go project with a command-line program, documentation templates, examples, and tests. The guide describes its folders, build commands, formatting rules, and test command.

In plain words
What is it for?
They help build and install the Hype command-line program, run its tests, regenerate documentation, inspect command options, and follow the project’s Go conventions.
Why use it?
They make the project’s structure and expected development checks explicit. This helps an agent avoid putting code in the wrong package or skipping race, coverage, and other test checks.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is gopherguides/hype's own configuration. It tells Codex and OpenCode how to work on hype itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hype configures →

not rated 59repo 7d ago A scan 552 tokens original MIT
View source ↗ gopherguides/hype
Reuse

Borrowing it

Nothing to install: this file belongs to gopherguides/hype. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gopherguides/hype/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/gopherguides/hype

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for hype AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gopherguides/hype/agents-md/github.svg)](https://agentmods.dev/instructions/gopherguides/hype/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/gopherguides/hype/agents-md"><img src="https://agentmods.dev/badge/instructions/gopherguides/hype/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.

agentmods 80×15 button for hype AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gopherguides/hype/agents-md"><img src="https://agentmods.dev/badge/instructions/gopherguides/hype/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 552 This file is loaded in full into every session.
When invoked 552 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00552 $0.00552
Opus 5.5 $0.00221 $0.00221
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

Measured 2mo ago against content hash 96bd0ed261ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

AGENTS.md · 26 lines

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: runs go test -count 1 -race -vet=off -cover across all packages except generated docs.
  • make build: produces a local hype binary from cmd/hype/.
  • go run ./cmd/hype --help: inspect CLI options without installing.
  • make docs or make hype: regenerate README.md from hype.md; run after changing documentation templates.
  • go install ./cmd/hype: install the CLI into your $GOBIN for 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

Read the full file on GitHub · 26 lines

Changes

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.

  1. 2mo ago First seen · 26 lines · 552 tokens per session scan A 96bd0ed261ae

Subscribe to this mod's changes

hype AGENTS.md is an instructions file published in the GitHub repository gopherguides/hype (59 stars, last pushed 7d ago), licensed MIT. It adds 552 tokens to every session, about $0.0022 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.

Related

hype AGENTS.md compared with instructions from other repositories

hype AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
hype AGENTS.mdgopherguides/hypeInstructions file597d agoMITA552Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode