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/flornkm/shadow-plugin/agents-mdgit clone --depth 1 https://github.com/flornkm/shadow-pluginWhat 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.00524 | $0.00524 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
shadow-plugin 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.
How it starts
The opening of the file, as written. The whole thing — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shadow Agent Instructions
Dev environment tips
- Run
npm install shadow-plugin(or your preferred package manager) to add the package to your workspace so Vite, ESLint, and TypeScript can see it - In the CSS file, which includes
@import "tailwindcss";, add the following line:@import "shadow-plugin";
CSS (tailwind) class instructions
- Use
smooth-shadow, or the size variantssmooth-shadow-xsup tosmooth-shadow-2xl - Color the shadow with tokens like
shadow-red-500 - For elevated surfaces (dialogs, popovers, cards, menus) use
smooth-shadow-ringor the size variantssmooth-shadow-ring-xsup tosmooth-shadow-ring-2xl, the shadow with a 1px hairline ring baked in; never add aborder/ringto the same element - Color the ring independently from the shadow with
smooth-ring-{color}, e.g.smooth-ring-black/10 - The hairline follows the project's
--default-ring-widthautomatically (1px if unset); override--smooth-ring-widthonly when it must differ from the project ring width - The utilities carry no
!importantand follow the normal cascade. If one must win against CSS that outranks it (a component library's ownbox-shadow), use Tailwind's important modifier on that element —smooth-shadow-md!— rather than a global override - To replace Tailwind's own shadow scale instead of adding new class names, import
shadow-plugin/unprefixedand use the nativeshadow-{size}utilities (this keepsshadow-md/40andshadow-{color}working; a@theme { --shadow-md: var(--smooth-shadow-md); }remap does not)
Avoid double borders
- A
border-*(orring-*) next to ashadow-*on the same element draws two stacked edges: a hard line, then the shadow starting just outside it. That double border reads heavy and greyed - Whenever you would pair a border/ring with a shadow on an elevated surface, use
smooth-shadow-ring-{size}instead. It bakes a 1px hairline ring into the shadow's final layer so the edge dissolves into one continuous stroke - The reusable skill lives at
.claude/skills/smooth-shadow-ring/SKILL.md; the Cursor Bugbot rule lives atBUGBOT.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 · 23 lines · 524 tokens per session scan A f82b3c2a2411
shadow-plugin AGENTS.md is an instructions file published in the GitHub repository flornkm/shadow-plugin (133 stars, last pushed 28d ago), licensed MIT. It adds 524 tokens to every session, about $0.0026 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
electron copilot-instructions.md
Instructions for electron/electron, covering copilot instructions for electron, build system, linting, running a single test and example: npm run test -- -g "ipc".
biome AGENTS.md
Instructions for biomejs/biome, covering agent guidelines for contributing to biome, communication, before editing, implementation gate and final review.
nuxt-starter CLAUDE.md
Instructions for lazercaveman/nuxt-starter, covering claude.md — nuxt-starter, project, tech stack, directory layout and commands.
starling AGENTS.md
Instructions for starling-browser/starling, covering agents — rules of engagement, tl;dr, 1. orient, 2. claim something unblocked and 3. read the package file and start working on main.
ReadMeABook AGENTS.md
AGENTS.md instructions for kikootwo/ReadMeABook, covering readmeabook agent instructions and shared developer docker compose.
poster-maker CLAUDE.md
Instructions for dabodamjan/poster-maker, covering poster maker, project purpose, project structure, commands and key rules.