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/francescogabrieli/glyph/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/francescogabrieli/glyph/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/francescogabrieli/glyph/copilot-instructions.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.00823 | $0.00823 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
glyph copilot-instructions.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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
This project uses React, TypeScript, Node, ESLint, Playwright, and npm. Follow existing style, keep the PR focused, and avoid broad rewrites. Read files before editing and plan before editing shared state or routing.
Development commands
| purpose | command |
|---|---|
| install dependencies | npm install |
| run local app | npm run dev |
| run tests | npm test |
| lint code | npm run lint |
| type check | npm run typecheck |
| build production bundle | npm run build |
Pull request checks
Before opening a PR, make sure the suite is green. Run lint before completion and typecheck before completion. Report changes and report verification in the final response. If tests cannot be run, explain why.
Safety
Never include credentials, API keys, tokens, private keys, or secrets in code, tests, logs, fixtures, examples, screenshots, or docs. Ask before destructive operations or security-sensitive authorization changes. Do not deploy without approval.
Avoid generated files unless explicitly requested. Use shared UI primitives where possible.
Context
The application has several product areas with different maturity levels. New screens usually use the latest shared primitives, while older screens may contain local wrappers that are being retired. Accessibility notes explain keyboard behavior, dialog focus management, and status messaging. The instructions above capture agent-relevant workflow rules; the surrounding text gives maintainers enough context to judge generated changes.
Some generated clients are committed because downstream tooling reads them during local development. Humans decide when regeneration is appropriate. Generic coding agents should not silently infer that every generated file is safe to edit. Glyph reports repository-specific operational language as unmapped unless a custom rule teaches the project-specific meaning.
Repository rules
Read relevant files before editing. Keep changes small and reviewable. Prefer existing patterns and use shared UI primitives where possible. Preserve accessibility behavior, including keyboard navigation, focus order, labels, and screen-reader text.
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 · 64 lines · 823 tokens per session scan A dcc40b9530e5
glyph copilot-instructions.md is an instructions file published in the GitHub repository francescogabrieli/glyph (7 stars, last pushed 1mo ago), licensed MIT. It adds 823 tokens to every session, about $0.0041 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
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).
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 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
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.
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.
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.