Borrowing it
Nothing to install: this file belongs to francescogabrieli/glyph. 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/francescogabrieli/glyph/main/AGENTS.mdgit clone --depth 1 https://github.com/francescogabrieli/glyphWrote 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/francescogabrieli/glyph/agents-md)<a href="https://agentmods.dev/instructions/francescogabrieli/glyph/agents-md"><img src="https://agentmods.dev/badge/instructions/francescogabrieli/glyph/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.02005 | $0.02005 |
| Opus 5 | $0.01002 | $0.01002 |
| Sonnet 5 | $0.00401 | $0.00401 |
| Haiku 4.5 | $0.00200 | $0.00200 |
Grade A, and why
glyph 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 6d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on Glyph
Glyph is a production-quality, open-source Instructions-as-Code toolchain for
coding-agent instruction files. It compiles verbose Markdown guidance into
compact, versioned .glp semantic manifests while preserving measurable
operational semantics.
This file is the operating contract for contributors and coding agents working in this repository. Product and user documentation lives in docs/README.md.
Product contract
Glyph must make instruction files:
- smaller and measurable;
- lintable, diffable, benchmarkable, and enforceable in CI;
- portable through Markdown compatibility emitters;
- deterministic and auditable;
- safe to evolve without silent semantic loss.
Glyph preserves measurable operational semantics. It does not preserve arbitrary prose, guarantee identical LLM behavior, or promise a fixed token reduction.
Never weaken these product boundaries:
- no LLM calls, remote API calls, or network dependencies in the library, compiler, or benchmarks;
- no silent candidate drops or lossy v0.2-to-v0.1 downgrade;
- no corpus-specific phrases, repository identities, or third-party source text in committed code, fixtures, reports, or tests;
- no lowering a gate merely to make a result green;
- no conversion of ambiguous relations into opaque target strings.
Documentation map
Read the relevant document before changing the associated behavior.
| Area | Documentation |
|---|---|
| Product onboarding and public claims | README, docs hub, FAQ |
| Format and compatibility | .glp spec, v0.1 spec, compatibility |
| 0.2 policy semantics | policy architecture |
| Extraction and retention | extraction engine, no silent loss |
| CLI, config, rules, CI | CLI reference, configuration, custom rules, CI guide |
| Architecture and security | architecture, security model |
| Development and validation | development, testing, release process |
| Corpus and benchmark evidence | benchmark methodology, corpus harness, static-gate report |
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.
- 6d ago First seen · 240 lines · 2,005 tokens per session scan A 5c20d165b9b1
glyph AGENTS.md is an instructions file published in the GitHub repository francescogabrieli/glyph (7 stars, last pushed 1mo ago), licensed MIT. It adds 2,005 tokens to every session, about $0.0100 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-31.
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.
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.