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/knopki/agent-skills/agents-mdgit clone --depth 1 https://github.com/knopki/agent-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/knopki/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/knopki/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/knopki/agent-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.00565 | $0.00565 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
agent-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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
Agent Skills repository in Agent Skills format.
How to use this repository
-
Skills are located at
skills/ -
Agent-visible paths:
.agents/skills/.claude/skills/
-
Setup virtual env via
uv -
Use
uv run agentskills-ci score --min-score 80 ./skillsto validate skills -
Use
uv run mdlint check skills/**/*.mdto validate skill's markdown files -
Use
ruff,zuban,pytestto lint/test skill's scripts -
Skills are reusable and independent
When solving tasks:
- Identify if a relevant skill exists
- Prefer using a skill over improvising
- Follow the skill strictly once selected
Output quality
Always:
- prioritize correctness over verbosity
- surface risks and uncertainties explicitly
- structure outputs (sections, bullet points)
- avoid vague statements
Safety and scope
- Do not assume access to external systems unless explicitly provided
- Do not fabricate data (PRs, logs, metrics, etc.)
- Clearly state assumptions
Modification rules
When editing this repository:
- keep skills portable (vendor-neutral)
- do not introduce agent-specific logic into
SKILL.md - place agent-specific config under
skills/<name>/agents/ - keep
.agents/skills/and.claude/skills/symlinks in sync withskills/ - prefer repo-provided tooling from the
uv run
Adding new skills
When creating a skill:
- ensure
descriptionis an activation rule - include:
- "When to use"
- "Steps"
- "Output"
- avoid duplication with existing skills
- consult the Agent Skills references instead of duplicating their guidance here:
- Specification: https://agentskills.io/specification
- Optimizing descriptions: https://agentskills.io/skill-creation/optimizing-descriptions
- Best practices: https://agentskills.io/skill-creation/best-practices
- use repository tooling where applicable:
- git hooks for baseline checks
agentskillsCLI from the dev environment
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 · 91 lines · 565 tokens per session scan A 687a75594a6a
agent-skills AGENTS.md is an instructions file published in the GitHub repository knopki/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 565 tokens to every session, about $0.0028 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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.