Borrowing it
Nothing to install: this file belongs to zackabrah/scopeglass. 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/zackabrah/scopeglass/main/AGENTS.mdgit clone --depth 1 https://github.com/zackabrah/scopeglassWrote 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/zackabrah/scopeglass/agents-md)<a href="https://agentmods.dev/instructions/zackabrah/scopeglass/agents-md"><img src="https://agentmods.dev/badge/instructions/zackabrah/scopeglass/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/zackabrah/scopeglass/agents-md"><img src="https://agentmods.dev/badge/instructions/zackabrah/scopeglass/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.00424 | $0.00424 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
scopeglass 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.
What it actually says
Scopeglass contributor instructions
Project
Scopeglass is a local-only Node.js/TypeScript CLI for inspecting hierarchical
AGENTS.md scope. The source of truth is SPEC.md; the ordered implementation
plan is tasks/plan.md.
Commands
- Install:
npm ci - Test:
npm test - Coverage:
npm run test:coverage - Lint:
npm run lint - Format check:
npm run format:check - Typecheck:
npm run typecheck - Build:
npm run build - Package check:
npm run package:check - Full verification:
npm run verify
Conventions
- Use TypeScript ESM and named exports in library modules.
- Keep the functional analysis core separate from filesystem/process boundaries.
- Validate external values once at the boundary; internal code relies on typed
contracts from
src/types.ts. - Write a failing behavioral test before implementation.
- Preserve stable JSON schema fields, diagnostic codes, and CLI exit codes.
- Keep repository-derived content visibly untrusted and escaped in every output.
- Prefer small focused modules and explicit data flow over framework patterns.
export function normalizeDisplayPath(
root: string,
absolutePath: string,
): string {
return path.relative(root, absolutePath).split(path.sep).join("/") || ".";
}
Boundaries
Always
- Resolve and contain paths before reading.
- Cap input sizes and test abuse cases.
- Run the relevant focused test after each behavior change.
- Run
npm run verifybefore declaring the release candidate complete.
Ask first
- Add a runtime dependency.
- Change public JSON, diagnostics, commands, or exit semantics.
- Add a new scanned instruction format or vendor profile.
Never
- Execute, import, or fetch content referenced by a scanned repository.
- Add telemetry, remote assets, model calls, or runtime network access.
- Use
innerHTMLwith repository-derived content. - Weaken or delete a failing test to make verification pass.
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.
- 2mo ago First seen · 62 lines · 424 tokens per session scan A 645a2dd012e6
scopeglass AGENTS.md is an instructions file published in the GitHub repository zackabrah/scopeglass (2 stars, last pushed 12d ago), licensed MIT. It adds 424 tokens to every session, about $0.0017 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-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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.