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/ohmiler/gridgeist/agents-mdgit clone --depth 1 https://github.com/ohmiler/gridgeistWhat 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.00141 | $0.00141 |
| Opus 5 | $0.00071 | $0.00071 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
gridgeist 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 2d 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
Project instructions
- Do not use any
superpowers:*skills in this repository. - Do not create or restore files under
docs/superpowers/. - Use the
solodevelingskill at the start of every task in this repository. Resume.solodeveling/state.mdwhen present and let the skill route the work to the smallest relevant lifecycle workflow. - Keep one primary agent. Do not use subagents unless the user explicitly requests delegation.
- If
solodevelingis unavailable, state that briefly and continue with the same evidence-driven lifecycle rather than blocking routine work. - Work directly from the user's request and use only the minimum additional relevant skills.
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.
- 2d ago First seen · 9 lines · 141 tokens per session scan A 6eae41c4a48c
gridgeist AGENTS.md is an instructions file published in the GitHub repository ohmiler/gridgeist (114 stars, last pushed 1mo ago), licensed MIT. It adds 141 tokens to every session, about $0.0007 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
MasterGo2Figma AGENTS.md
AGENTS.md instructions for AaronXu-Lab/MasterGo2Figma, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
MasterGo2Figma CLAUDE.md
Claude Code instructions for AaronXu-Lab/MasterGo2Figma: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
starwind-ui AGENTS.md
Instructions for starwind-ui/starwind-ui, covering agents.md, project shape, useful commands and contribution conventions.
wonder-blocks storybook.instructions.md
Storybook best practices for Wonder Blocks component stories.
wonder-blocks AGENTS.md
Instructions for Khan/wonder-blocks, covering wonder blocks – agentic workflows & storybook mcp, installing the mcp (consumer setup), storybook mcp server, when it’s available and mcp endpoint.