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/sayhi-bzb/agent-html/agents-mdgit clone --depth 1 https://github.com/Sayhi-bzb/Agent-HTMLWrote 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/sayhi-bzb/agent-html/agents-md)<a href="https://agentmods.dev/instructions/sayhi-bzb/agent-html/agents-md"><img src="https://agentmods.dev/badge/instructions/sayhi-bzb/agent-html/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 | $0.00530 | $0.00530 |
| Opus 5 | $0.00265 | $0.00265 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
Agent-HTML 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus
This repo is indexed by GitNexus as Agent-HTML. Use GitNexus MCP for code exploration, impact analysis, and change verification.
Rules:
- Before editing any function, class, method, or shared API, run
gitnexus_impact({ target: "<symbol>", direction: "upstream" }). - Before finishing a code-change task, run
gitnexus_detect_changes({ scope: "all" })and confirm the affected scope is expected. - If the index is stale, re-index only with
npx gitnexus analyze --skip-agents-md. - Do not run bare
npx gitnexus analyze; it rewrites the GitNexus sections inAGENTS.mdandCLAUDE.md.
Useful resources:
gitnexus://repo/Agent-HTML/contextgitnexus://repo/Agent-HTML/processesgitnexus://repo/Agent-HTML/process/{name}
Docs Writing Rules
Apply these rules when writing or editing docs.
- Use high-information wording that locks direction with the fewest sufficient terms.
- Do not add broad, repeated, or low-marginal words when existing terms already identify the concept.
- Keep one source of truth for each fact, principle, or decision; link to it instead of restating it.
- Keep one stable name for each concept.
- Keep route files narrow: one page should own one kind of question.
- Write docs as agent context routes and owner maps. Human-readable prose is the interface agents parse, cite, and follow.
- Avoid human-oriented background or tutorial framing unless it changes the next correct agent action.
- Prefer restrained, minimal, sufficient writing over exhaustive explanation.
Content Routes
Use the smallest route for the task before searching broadly.
- Canvas:
apps/docs/content/docs/index.mdx, thenagent-html/README.md - Taste and agent ergonomics:
taste/README.md - Archive:
_archive/README.md
Canvas Constitution
Canonical source: apps/docs/content/docs/index.mdx.
Canvas governs the current isolated React artifact workspace for agents. Use
the canonical source before changing Canvas docs, agent-html, artifact/block
composition, local resources, host inspection, or block prompt behavior.
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.
- 5d ago First seen · 55 lines · 530 tokens per session scan A 02f66e9ace76
Agent-HTML AGENTS.md is an instructions file published in the GitHub repository Sayhi-bzb/Agent-HTML (542 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 530 tokens to every session, about $0.0027 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
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
SeekMoney-ai CLAUDE.md
Claude Code instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
slivingdoc AGENTS.md
AGENTS.md instructions for baalimago/slivingdoc, covering agents.md — slivingdoc, architecture, package map, event flow and startup wiring (main.go).