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/ludusrusso/wildgecu/agents-mdgit clone --depth 1 https://github.com/ludusrusso/wildgecuWrote 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/ludusrusso/wildgecu/agents-md)<a href="https://agentmods.dev/instructions/ludusrusso/wildgecu/agents-md"><img src="https://agentmods.dev/badge/instructions/ludusrusso/wildgecu/agents-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 | $0.00020 | $0.00020 |
| Opus 5 | $0.00010 | $0.00010 |
| Sonnet 5 | $0.00004 | $0.00004 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
wildgecu 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 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
Use subtesting instead of pattern like TextXXX_YyY
Always use git Conventional Commits
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 · 4 lines · 20 tokens per session scan A 58dca731d67e
wildgecu AGENTS.md is an instructions file published in the GitHub repository ludusrusso/wildgecu (21 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 20 tokens to every session, about $0.0001 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
presidio recognizers.instructions.md
Instructions for data-privacy-stack/presidio, covering recognizer changes, the load-bearing rule: test the configuration path, placement and naming, pattern scores and context words.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
technocore-chat AGENTS.md
Instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
agent-rules testing.instructions.md
Instructions for lirantal/agent-rules, covering testing guidelines for node.js applications, general testing principles, guiding principles, descriptive test naming (three-part structure) and structure tests by the aaa pattern.
instrMCP CLAUDE.md
Instructions for caidish/instrMCP, covering claude.md, development commands, always use conda environment instrmcpdev for testing, unit tests (fast, no hardware required - all mocked) and e2e tests (requires playwright and browser automation).
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.