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/flc1125/skills/agents-mdgit clone --depth 1 https://github.com/flc1125/skillsWrote 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/flc1125/skills/agents-md)<a href="https://agentmods.dev/instructions/flc1125/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/flc1125/skills/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.00662 | $0.00662 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
skills 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 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.
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 — 20 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository combines a small Next.js marketplace app with installable skill content. The marketplace now lives under web/: routes, layout, and global styles are in web/src/app, reusable UI components in web/src/components, and parsing/helpers in web/src/lib. Static assets are under web/public/. Documentation lives in docs/. Each installable skill lives in skills/<skill-name>/ and should include a SKILL.md; related references, docs, and agent configs stay beside it. The repository root doubles as a plugin for both Claude Code (.claude-plugin/) and Codex (.codex-plugin/, .agents/plugins/marketplace.json), each exposing the shared skills/ directory; keep the manifests in sync when the plugin identity changes.
Build, Test, and Development Commands
Run marketplace commands from web/. Use cd web && npm install to install dependencies. Run cd web && npm run dev to start the local Next.js server at http://localhost:3000. Run cd web && npm run lint for the primary quality gate with ESLint 9 and Next.js rules. Run cd web && npm run build to verify production output. In restricted environments where Turbopack build workers fail, use cd web && npx next build --webpack as a fallback.
Coding Style & Naming Conventions
Write TypeScript and React with 2-space indentation omitted in favor of the repository’s current style: concise files, semicolons, and single quotes. Keep React components and files in PascalCase, such as SkillCard.tsx; utility modules use lowercase names such as utils.ts. Prefer App Router conventions in web/src/app, and keep skill directory names kebab-case, matching the skill install name where possible.
Testing Guidelines
There is no dedicated automated test suite yet. Treat cd web && npm run lint and cd web && npm run build as required validation before opening a PR. For content changes, manually verify the affected skill page and confirm the SKILL.md frontmatter parses correctly. If you add tests later, place them near the relevant module or in a clearly named tests/ directory and use descriptive names like skills-api.test.ts.
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 · 20 lines · 662 tokens per session scan A ba465a63b8d5
skills AGENTS.md is an instructions file published in the GitHub repository flc1125/skills (36 stars, last pushed today), licensed MIT. It adds 662 tokens to every session, about $0.0033 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
rolecraft AGENTS.md
Instructions for rolecraft-sh/rolecraft, covering rolecraft — development guidelines, ⚠️ startup checklist (read before every task), workflow, interaction rules and code style.
claude-skills CLAUDE.md
Instructions for obeone/claude-skills, covering claude.md, repository overview, architecture, current skills and commands.
exa-research-mcp-skill AGENTS.md
AGENTS.md instructions for liangdabiao/exa-research-mcp-skill, covering repository agent guide, key locations, editing rules and testing.
agent-skills-android CLAUDE.md
Instructions for GuillemRoca/agent-skills-android, a project described as: Production-grade engineering skills for AI coding agents tailored to Android.
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.