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/paullukic/coograph/stylinggit clone --depth 1 https://github.com/paullukic/coographWhat 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 | $0.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
coograph styling.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 3d 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
Styling Conventions
Template guard: This file is a stub — all rules are commented out. Uncomment and customize the rules that apply to your project before relying on this file, or delete it if the project does not use styling conventions. Agents loading this file while it is still stubbed should flag it to the user.
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.
- 3d ago First seen · 34 lines · 320 tokens per session scan A 567f087bf98e
coograph styling.instructions.md is an instructions file published in the GitHub repository paullukic/coograph (17 stars, last pushed 27d ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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
tidyfactor-design AGENTS.md
Instructions for alwkala/tidyfactor-design, covering ⚡ skill & 24 modular slash commands (7 lifecycle stages) and critical architecture (non-negotiable).
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
snip CLAUDE.md
Instructions for edouard-claude/snip, covering claude.md, project overview, key concept, repository structure and architecture.
AmbyKit AGENTS.md
Instructions for ambystechcom/AmbyKit, covering agents.md — ambykit, what ambykit is, golden rules, project structure and build & test.
codemap AGENTS.md
Instructions for stainless-code/codemap, a project described as: Cut AI-agent token waste 90% — query a local SQLite structural index of your JS/TS/CSS codebase with SQL in one round-trip instead of 3–5 file reads. Symbols, imports, calls, components, CSS tokens, coverage, markers. CLI, MCP (21 tools), HTTP, GitHub…
agent-notify AGENTS.md
AGENTS.md instructions for Akash97p/agent-notify, covering agentnotify agent workflow, start or resume work, local git workflow, required quality gates and architecture and security guardrails.