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/pauljphilp/effectpatterns/agents-mdgit clone --depth 1 https://github.com/PaulJPhilp/EffectPatternsWhat 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.00160 | $0.00160 |
| Opus 5 | $0.00080 | $0.00080 |
| Sonnet 5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
EffectPatterns 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
AGENTS.md
For architecture, agents, integration, config, testing, deployment, security, monitoring, and development guidelines, use:
- docs/Architecture.md – single source for all architecture and agent context.
- docs/Effect-Patterns-Rules.md – canonical Effect Patterns rules for all AI tools.
Run commands from the project root. Use Bun and workspace:* dependencies; no TypeScript path aliases.
Below: generated Effect Patterns rules (do not edit by hand).
For Effect Patterns rules, see docs/Effect-Patterns-Rules.md.
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 · 18 lines · 160 tokens per session scan A 65d72a98635d
EffectPatterns AGENTS.md is an instructions file published in the GitHub repository PaulJPhilp/EffectPatterns (795 stars, last pushed 2mo ago), licensed MIT. It adds 160 tokens to every session, about $0.0008 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
pi-effect-harness AGENTS.md
Instructions for mpsuesser/pi-effect-harness, covering agents.md — pi-effect-harness, layout, verification, where to look for common changes and conventions.
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
llm-wiki-agent GEMINI.md
Gemini CLI instructions for SamurAIGPT/llm-wiki-agent, covering llm wiki agent — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.
huly-mcp CLAUDE.md
Instructions for dearlordylord/huly-mcp, covering project instructions, design principle: llm-first api, project harness (copy to new projects), package manager and verification.
DocMason copilot-instructions.md
Instructions for JetXu-LLM/DocMason, covering docmason github copilot notes and copilot-specific delta.
DeepRefine-Skill GEMINI.md
Instructions for HKUST-KnowComp/DeepRefine-Skill, covering deeprefine skill for gemini cli, core behavior and commands.