Borrowing it
Nothing to install: this file belongs to lynx-family/lynx-website. 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/lynx-family/lynx-website/main/AGENTS.mdgit clone --depth 1 https://github.com/lynx-family/lynx-websiteWrote 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/lynx-family/lynx-website/agents-md)<a href="https://agentmods.dev/instructions/lynx-family/lynx-website/agents-md"><img src="https://agentmods.dev/badge/instructions/lynx-family/lynx-website/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.
<a href="https://agentmods.dev/instructions/lynx-family/lynx-website/agents-md"><img src="https://agentmods.dev/badge/instructions/lynx-family/lynx-website/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01000 | $0.01000 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
lynx-website 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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Downstream Compatibility
This repository is consumed by the in-house Lynx documentation site through a
pinned git submodule and local file: dependency.
Directly Consumed Paths
The downstream prepare flow consumes these OSS paths:
- Copied or merged content:
docs/,i18n.json, andsharedDocs/ - Symlinked runtime:
src/andtheme/ - Imported configuration:
tailwind.config.js - Package contract:
package.json - Generated-data inputs:
packages/lynx-living-spec/,packages/lynx-compat-data/,packages/lynx-example-packages/,packages/lynx-ui-example-packages/, andpackages/lynxtron-example-packages/
The downstream repository replaces docs/public/lynx-examples and applies
internal content overlays after copying OSS content.
Downstream Tool Contract
The downstream prepare flow directly executes:
scripts/luna-demo.jsscripts/lynx-example.js
The downstream directly executes scripts/lynx-living-spec.js from its
installed lynx-doc dependency through its own Living Spec orchestration layer.
It prepares downstream source overlays first and runs the generator with the
downstream repository root as the working directory.
Keep these script paths, caller-working-directory behavior, environment variables, and generated output layouts compatible with downstream callers.
api-stats.json doc links
packages/lynx-compat-data's gen-stats emits a doc_url per API. When the
caller supplies a docs root — via --docs-root <dir> (resolved against the
working directory) or LYNX_COMPAT_DOCS_ROOT — it emits only the URLs that
resolve to a route in that tree; without one it emits every URL unchecked. The
OSS site supplies its own root through the gen:compat-stats script, which is
therefore the script to use when regenerating these stats by hand. The root is
never inferred from the package's location, so an install layout cannot decide
which routes the data is checked against.
A consumer that generates these stats itself should pass its own docs root, and
gets a doc_url set matching the pages it publishes. Omitting the option skips
verification and emits every URL unchecked; naming a root that does not exist
is an error rather than a silent skip, so a run either verifies against the
tree it was told to use or does not verify at all.
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.
- yesterday Changed · +5 lines · +67 tokens per session 1973d7603f1e
- 10d ago First seen · 106 lines · 933 tokens per session scan A 98f6e492a408
lynx-website AGENTS.md is an instructions file published in the GitHub repository lynx-family/lynx-website (130 stars, last pushed today), licensed Apache-2.0. It adds 1,000 tokens to every session, about $0.0050 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
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.