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/jal-co/shieldcn/agents-mdgit clone --depth 1 https://github.com/jal-co/shieldcnWrote 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/jal-co/shieldcn/agents-md)<a href="https://agentmods.dev/instructions/jal-co/shieldcn/agents-md"><img src="https://agentmods.dev/badge/instructions/jal-co/shieldcn/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.03709 | $0.03709 |
| Opus 5 | $0.01854 | $0.01854 |
| Sonnet 5 | $0.00742 | $0.00742 |
| Haiku 4.5 | $0.00371 | $0.00371 |
Grade A, and why
shieldcn AGENTS.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://localhost:3000/badge/label-value-COLOR.svg?variant=outline&mode=light" | grep -oE 'fill="[^"]*"' How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — shieldcn
What this is
shieldcn is a Turborepo monorepo that serves styled SVG/PNG badge images for use in GitHub READMEs, npm pages, and docs sites. It's a shields.io alternative where badges are rendered as actual shadcn/ui Button components via Satori.
Monorepo Structure
shieldcn/
├── packages/
│ ├── core/ ← @shieldcn/core — shared badge engine library
│ ├── web/ ← @shieldcn/web — marketing site (Vercel)
│ └── engine/ ← @shieldcn/engine — self-hosted Docker image
├── turbo.json
├── pnpm-workspace.yaml
└── ...
packages/core (@shieldcn/core)
Shared badge engine consumed by both web and engine. No build step — raw TypeScript consumed via transpilePackages.
- Badge renderer (
src/badges/render.tsx) — React components → SVG via Satori. Uses Inter Medium font. Every badge goes through oneresolve()function then onerenderSingle()orrenderSplit()function. No variant-specific render paths. - Button tokens (
src/badges/button-tokens.ts) — Exact shadcn Button design tokens (bg, fg, border per variant) resolved to hex values for both dark and light mode. - Icon resolution (
src/badges/simple-icons.ts) — Two sources: SimpleIcons (2400+) and React Icons (40,000+). Prefix convention: bare slug = SimpleIcons,ri:ComponentName= React Icons. - Data providers (
src/providers/) — npm, GitHub, Discord, Reddit, static badges, dynamic JSON, HTTPS endpoint, memo badges. Each returns{ label, value, color?, link? }. - Token pool (
src/token-pool.ts) — GitHub OAuth token pool stored in Postgres. Distributes API requests across many user-donated tokens to stay under rate limits. - Route handler (
src/route-handler.ts) — ReusablehandleBadgeGET()/handleBadgePUT()that parses URLs, fetches data, resolves icons/colors/variants, renders SVG/PNG/JSON. Accepts optionalonTrackcallback for analytics. - Cache (
src/cache.ts) — Two-tier caching (in-memory LRU + optional Upstash Redis) with per-provider backoff and rate budgets. - Format (
src/format.ts) —formatCount()number formatting (single source of truth).
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.
- 4d ago First seen · 266 lines · 3,709 tokens per session scan A 2025059b669c
shieldcn AGENTS.md is an instructions file published in the GitHub repository jal-co/shieldcn (842 stars, last pushed 7d ago), licensed MIT. It adds 3,709 tokens to every session, about $0.0185 per session on Opus 5. A static security scan graded it A with 1 finding (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
mainbranch AGENTS.md
Instructions for noontide-co/mainbranch, covering agent instructions, product shape, daily operating loop, quick start and repository layout.
markdown-site CLAUDE.md
Instructions for waynesutton/markdown-site, covering claude.md, project context, quick start, commands and default and legacy modes.
mainbranch CLAUDE.md
Instructions for noontide-co/mainbranch, covering claude code instructions, repository role, product loop to preserve, how to work here and engine vs business repo.
markdown-site AGENTS.md
Instructions for waynesutton/markdown-site, covering agents.md, project overview, default and legacy modes, current status and tech stack.
abap2UI5 CLAUDE.md
Instructions for abap2UI5/abap2UI5: All project guidance lives in AGENTS.md — the single source of truth for this repository (architecture and the layered design, the src/00-99 packages, the generated app/webapp mirror, the build and delivery pipeline, the CI gates and ABAP code style).
namescope AGENTS.md
AGENTS.md instructions for ensp1re/namescope: This repository uses the project harness in .ai/. Codex must operate that harness automatically; the user should only need to describe work normally. Read .ai/README.md before repository-changing work.