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/liwala/sheal/agents-mdgit clone --depth 1 https://github.com/liwala/shealWhat 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.02989 | $0.02989 |
| Opus 5 | $0.01494 | $0.01494 |
| Sonnet 5 | $0.00598 | $0.00598 |
| Haiku 4.5 | $0.00299 | $0.00299 |
Grade B, and why
sheal AGENTS.md scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- [LEARN-017] When working inside a container or VM, run `cat /etc/os-release && which sudo docker git` as the first command to inventory the environment — do not assume any tool exists. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [LEARN-001] Before writing parsers for external data formats (JSON APIs, JSONL transcripts, config files), always inspect 2-3 real samples first using git show, curl, or cat. How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
See also: @CLAUDE.md for Claude Code-specific instructions.
Agent Operating Policy
1. TDD discipline — strict order
For any behavior with a clear, assertable contract (bug fixes, business logic, API or CLI behavior):
- Write the test that asserts the intent of the behavior.
- Run the suite. Confirm the new test fails — for the right reason (not a typo, import error, or unrelated failure).
- Only then write the source that makes it pass.
- Run the suite again. Confirm it goes green.
A regression test added after the source fix is NOT TDD: it never failed, so it never proved the bug existed or that the fix addresses it. If you reach for the source first, stop — WRITE THE FAILING TEST FIRST.
The ONLY exception: spikes
For exploratory work where you don't yet know what the behavior should be (UI layout, prompt engineering, data exploration, unfamiliar APIs): spike to learn in a throwaway branch or scratch file, discard it, then TDD the real thing from scratch.
Declare a spike before starting, never after to excuse missing tests:
- State it up front: "Spike to learn X; I'll throw it away and TDD the real thing."
- Isolate it — never mixed into the production change.
- Show the discard before the real implementation lands.
An undeclared deviation is not a spike — it's skipped tests.
2. Tests assert intent
Tests assert intent (user-visible behavior), not implementation, and should survive a refactor. If a test breaks on a rename or internal reshuffle, rewrite it to assert observable behavior.
3. Never weaken a test to make it pass
Fix the code, never loosen an assertion, delete a case, or mock away the thing under test to go green. If the test itself is wrong, say so and explain why before changing it.
4. Version control
- Commit locally as you go, with focused, meaningful messages.
- Push only to a dedicated working branch — never to main or a shared branch. Gate every push on a green suite and a clean linter; never push with failing tests or lint errors.
- Scan for staged secrets/credentials before pushing (the linter won't catch these). In doubt, don't push — surface it.
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 · 227 lines · 2,989 tokens per session scan B 93152f150006
sheal AGENTS.md is an instructions file published in the GitHub repository liwala/sheal (86 stars, last pushed 1mo ago), licensed MIT. It adds 2,989 tokens to every session, about $0.0149 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
claude-ads CLAUDE.md
Instructions for AgriciDaniel/claude-ads, covering claude ads repository instructions, architecture, development and verification.
notebooklm-skill AGENTS.md
Instructions for claude-world/notebooklm-skill, covering notebooklm-skill, authentication, cli commands, notebooklm-skill — core operations and notebooklm-pipeline — workflow orchestration.
recursive-decomposition-skill AGENTS.md
Instructions for massimodeluisa/recursive-decomposition-skill, covering agents: recursive-decomposition skill, read these first (mandatory), language policy, non-negotiables and commands.
stockbit-mcp CLAUDE.md
Instructions for INo-xious/stockbit-mcp, covering claude.md, what this is, commands, the map and three invariants. do not break them; each has a test.
devin-handoff AGENTS.md
Instructions for club-cog/devin-handoff, covering devin handoff — agent guide, what this is, when to hand off, finding the script and how to use.
agent-plugins-skills copilot-instructions.md
Instructions for richfrem/agent-plugins-skills, covering copilot instructions for agent-plugins-skills, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.