shadow-plugin AGENTS.md

A set of instructions for using Shadow Plugin with a Vite, TypeScript, and Tailwind CSS project. It specifies the package import and Tailwind classes for shadows and thin rings around interface elements.

In plain words
What is it for?
Use it when adding or adjusting shadows, rings, cards, dialogs, popovers, menus, or other elevated interface surfaces.
Why use it?
It prevents incorrect setup and avoids adding a separate border where the plugin's combined shadow-and-ring utility already provides one.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/flornkm/shadow-plugin/agents-md
Clone the repo
git clone --depth 1 https://github.com/flornkm/shadow-plugin

Made for: Codex, OpenCode.

Per session 524 This file is loaded in full into every session.
When invoked 524 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash f82b3c2a2411, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 23 lines

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 variants smooth-shadow-xs up to smooth-shadow-2xl
  • Color the shadow with tokens like shadow-red-500
  • For elevated surfaces (dialogs, popovers, cards, menus) use smooth-shadow-ring or the size variants smooth-shadow-ring-xs up to smooth-shadow-ring-2xl, the shadow with a 1px hairline ring baked in; never add a border/ring to 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-width automatically (1px if unset); override --smooth-ring-width only when it must differ from the project ring width
  • The utilities carry no !important and follow the normal cascade. If one must win against CSS that outranks it (a component library's own box-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/unprefixed and use the native shadow-{size} utilities (this keeps shadow-md/40 and shadow-{color} working; a @theme { --shadow-md: var(--smooth-shadow-md); } remap does not)

Avoid double borders

  • A border-* (or ring-*) next to a shadow-* 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 at BUGBOT.md

Read the full file on GitHub · 23 lines

Changes

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.

  1. 2d ago First seen · 23 lines · 524 tokens per session scan A f82b3c2a2411

Subscribe to this mod's changes

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.