Borrowing it
Nothing to install: this file belongs to artemnovichkov/skills. 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/artemnovichkov/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/artemnovichkov/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/artemnovichkov/skills/agents-md)<a href="https://agentmods.dev/instructions/artemnovichkov/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/artemnovichkov/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.1 | $0.00496 | $0.00496 |
| Opus 5 | $0.00248 | $0.00248 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
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 7d 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.
Skills Marketplace
Curated collection of skills for AI coding agents. Each skill adds commands, hooks, MCP servers, or agents to enhance development workflows.
Compatible with 40+ agents via skills.sh: Claude Code, Codex, Cursor, Copilot, and more.
Repo Structure
skills/<skill-name>/
SKILL.md # Skill manifest for skills.sh (name, description, instructions)
.claude-plugin/plugin.json # Claude Code plugin manifest
README.md # Skill docs
commands/ # Slash commands (optional)
hooks/ # Hook definitions (optional)
.mcp.json # MCP server config (optional)
Root .claude-plugin/marketplace.json registers all skills for Claude Code plugin system.
Adding a New Skill
- Create
skills/<skill-name>/directory - Add
SKILL.mdwith frontmatter:--- name: <skill-name> description: Short description of what the skill does and when to use it --- # Skill Name Instructions for the agent... - Add
.claude-plugin/plugin.json(for Claude Code compatibility):{ "name": "<skill-name>", "description": "Short description", "version": "1.0.0" } - Add
README.mdwith features, requirements, usage - Add components:
commands/,hooks/,.mcp.jsonas needed - Register in
.claude-plugin/marketplace.jsonunderpluginsarray - Update root
README.mdwith skill listing
Installation
Any Agent (via skills.sh)
npx skills add artemnovichkov/skills
Claude Code
/plugin marketplace add artemnovichkov/skills
Conventions
SKILL.mdis the universal skill manifest (skills.sh ecosystem).claude-plugin/dirs andplugin.jsonare Claude Code conventions -- keep both for compatibility$CLAUDE_PLUGIN_ROOTenv var in hooks references skill root at runtime (Claude Code specific)- Keep skills self-contained (no cross-skill dependencies)
- Skills should document agent compatibility in their README
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.
- 7d ago First seen · 69 lines · 496 tokens per session scan A 22093ad85926
skills AGENTS.md is an instructions file published in the GitHub repository artemnovichkov/skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 496 tokens to every session, about $0.0025 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
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.
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.
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).
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).
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.
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.