Borrowing it
Nothing to install: this file belongs to frankxai/claude-skills-library. 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/frankxai/claude-skills-library/main/AGENTS.mdgit clone --depth 1 https://github.com/frankxai/claude-skills-libraryWrote 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/frankxai/claude-skills-library/agents-md)<a href="https://agentmods.dev/instructions/frankxai/claude-skills-library/agents-md"><img src="https://agentmods.dev/badge/instructions/frankxai/claude-skills-library/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/frankxai/claude-skills-library/agents-md"><img src="https://agentmods.dev/badge/instructions/frankxai/claude-skills-library/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.01581 | $0.01581 |
| Opus 5.5 | $0.00632 | $0.00632 |
| Sonnet 5.5 | $0.00316 | $0.00316 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
claude-skills-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 11d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inherited — Starlight estate contract
Identical in every repo in the estate. Authored once in
Starlight-Intelligence-System/ontology/agents-md/band-a.md and projected by
scripts/agents-md-project.mjs.
Precedence. Band C is everything below the generated fences. It outranks this section on any conflict inside this repo — a projected rule never silently overrides a local gate. It does not outrank the company projection below: that band carries registry facts, not instructions, so a Band C line contradicting it is a defect to fix upstream in the SIS registry, never a local override.
DNA
Frank = Systems Architect x Composer x Gamer x Builder x GenCreator
Vibe: cool, premium, high intellect, purpose-driven, fun. Mission: build abundance; help people build their own systems. Voice: direct, technical, warm, playful. Pattern recognition as poetry. Test: does this help someone build, not just consume?
The five guardrails
- Think before coding. State assumptions. Surface tradeoffs. If two readings exist, present both — do not pick silently.
- Explain simply. What you cannot explain plainly you do not understand. Name the mechanism, never "streamline" or "optimize".
- Simplicity and deep design. Minimum code that solves the stated problem. Simple interfaces, rich internals. No speculative abstraction.
- Surgical changes. Touch only what the task requires. Match surrounding style. Mention unrelated dead code; do not delete it.
- Goal-driven. Turn a vague ask into a verifiable target. Reproduce a bug with a test before fixing it.
Decision discipline
Before any structural change: what specific problem, who has it, what is the evidence, what is the simplest fix, what breaks, is it reversible. If it is not reversible, it needs Frank.
Branch and PR protocol
- Never push directly to
main. Work onagent/<harness>/<scope>, open a draft PR. - Run the repo's own gates before pushing. One validated push beats three speculative ones.
- Multiple harnesses work these repos at once; git is the coordination layer. Never two agents committing in the same working tree — take a non-overlapping scope on your own branch, integrate one at a time.
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.
- 11d ago Changed · +34 tokens per session 9033988ab1aa
- 19d ago Changed · +103 lines · +1,155 tokens per session da17b911ac40
- 1mo ago First seen · 43 lines · 392 tokens per session scan A da68fad0378b
claude-skills-library AGENTS.md is an instructions file published in the GitHub repository frankxai/claude-skills-library (47 stars, last pushed today), licensed MIT. It adds 1,581 tokens to every session, about $0.0063 per session on Opus 5.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
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.