Borrowing it
Nothing to install: this file belongs to liwala/sheal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/liwala/sheal/main/AGENTS.mdgit clone --depth 1 https://github.com/liwala/shealWrote 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/liwala/sheal/agents-md)<a href="https://agentmods.dev/instructions/liwala/sheal/agents-md"><img src="https://agentmods.dev/badge/instructions/liwala/sheal/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/liwala/sheal/agents-md"><img src="https://agentmods.dev/badge/instructions/liwala/sheal/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02989 | $0.02989 |
| Opus 5.5 | $0.01196 | $0.01196 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (88 stars, last pushed 3mo ago), licensed MIT. It adds 2,989 tokens to every session, about $0.0120 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.