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/justifi-tech/web-component-library/agents-mdgit clone --depth 1 https://github.com/justifi-tech/web-component-libraryWhat 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.01049 | $0.01049 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
web-component-library 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
web-component-library Agent Guidelines
Spec Authority
Specs are prescriptive, not descriptive. The spec defines what code MUST do.
- Spec is source of truth. If code contradicts the spec, the code is wrong — refactor it.
- Read the full spec on version changes. When the spec version is newer than specd_history.md, re-read the entire spec — not just the changelog. The changelog summarizes what changed, but context lives in the full spec.
- Don't build on broken foundations. If existing code uses the wrong model (e.g., wrong ID scheme, wrong data flow), fix it first. Don't add new features on top of incorrect code.
- Spec index:
specs/README.mdlists all specifications organized by phase. Only specs with status "Ready" should be implemented. - Changelogs are immutable. When creating new changelog entries, old entries never change.
Loop System
The autonomous loop is defined in loop.sh. Commands live in .claude/commands/:
| Command | Purpose |
|---|---|
/specd:implement |
Pick one unblocked work item, implement it, validate, record completion |
/specd:audit |
3-phase spec-vs-code audit. Writes findings to specd_work_list.md and specd_review.md |
/specd:review-intake |
Process specd_review.md items into specd_work_list.md |
specd_work_list.md (Remaining Work)
The single execution queue for all work — spec implementations, audit findings, and promoted review items. Read it in full at the start of each iteration — it is kept small. Pick an unblocked item, implement it, then move it to specd_history.md.
specd_history.md (Done Log)
specd_history.md is the archive of completed work in reverse chronological order (newest first). It does NOT contain remaining items — those live in specd_work_list.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 · 69 lines · 1,049 tokens per session scan A 382c11f2bf42
web-component-library AGENTS.md is an instructions file published in the GitHub repository justifi-tech/web-component-library (5 stars, last pushed 6d ago), licensed MIT. It adds 1,049 tokens to every session, about $0.0052 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-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.