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/nicholaspsmith/glancey/claude-mdgit clone --depth 1 https://github.com/nicholaspsmith/GlanceyWrote 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/nicholaspsmith/glancey/claude-md)<a href="https://agentmods.dev/instructions/nicholaspsmith/glancey/claude-md"><img src="https://agentmods.dev/badge/instructions/nicholaspsmith/glancey/claude-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.00431 | $0.00431 |
| Opus 5 | $0.00216 | $0.00216 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
Glancey CLAUDE.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.
What it actually says
Claude Code Preferences
⚠️ SESSION START - READ FIRST
Before making any changes, read .claude/rules.md for project standards.
Key requirements:
- NEVER commit directly to main - always create a feature branch first
- One responsibility per commit - split multiple changes into separate commits
- Use glancey for semantic code search, not Grep/Read for exploration
Command Preferences
Use modern CLI tools when available:
- Use
fdinstead offindfor file searching (faster, simpler syntax) - Use
rg(ripgrep) instead ofgrepfor content searching (faster, better defaults) - These tools are available on this system and should always be preferred
Semantic Code Search
This project uses glancey for semantic code search. When exploring the codebase:
- Use
search_codetool to find relevant code using natural language queries - Run
index_codebaseif the index appears out of date - Prefer semantic search over manual file exploration for understanding code patterns and finding implementations
OpenAI Policy
NEVER use any OpenAI products or services. This includes:
- OpenAI API (GPT models, embeddings, etc.)
- OpenAI SDKs or libraries
- ChatGPT
- DALL-E
- Whisper API
- Any other OpenAI service
For embeddings, use Jina or Ollama instead.
Pre-Commit Checklist
STOP! Before committing, verify:
- Read
.claude/rules.md(required every time) - On a feature branch, NOT main (
git branch --show-current) - Each commit has exactly ONE responsibility
- Subject line under 72 characters, imperative mood
- Body contains ONLY "Co-Authored-By: Claude [email protected]"
# Create feature branch first!
git checkout -b feature/your-feature-name
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 · 53 lines · 431 tokens per session scan A 9f5243f06015
Glancey CLAUDE.md is an instructions file published in the GitHub repository nicholaspsmith/Glancey (1 stars, last pushed 8d ago), licensed MIT. It adds 431 tokens to every session, about $0.0022 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).
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.
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.
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 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).