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/pproenca/dot-skills/agents-mdgit clone --depth 1 https://github.com/pproenca/dot-skillsWhat 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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
dot-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 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What This Repo Is
dot-skills is a curated collection of Agent Skills (markdown rule packs + scripts).
skills/.curated/— stable, published skillsskills/.experimental/— new / in-progress skills. New skills start here.- Skills are authored and evolved with the dev-skill plugin:
/dev-skill:new,:ingest,:evolve,:validate. - dev-skill disciplines: distillation / composition / investigation / extraction.
Don't mix disciplines in one skill dir — adding a
scripts/dir to a distillation skill flips its detected discipline and breaks validation. Build a sibling skill instead.
Definition of Done — run before every commit
When asked to "run all the skill validation and audit scripts" (or before committing skill changes):
npm run validate # skills-ref: structural validation of every skill
node scripts/check-versions.mjs # flag STALE/DIRTY skill versions
scripts/generate-readme-tables --update # regenerate README skill tables
npm test # skills-ref validator test suite
Fix every reported issue, then commit & push. A goal is not complete until verified.
Task Management
- Always use TaskCreate for any task with 2+ steps
- Break tasks into small, atomic units (carpaccio slicing)
- Each task should be completable in a single focused action
- Include acceptance criteria in task descriptions
- Set up task dependencies with addBlockedBy/addBlocks
Development Workflow — Validator-First
Most work here is authoring markdown rule files, so the validators are the test gate (the equivalent of red-green-refactor):
- Red — run the validator and read the failures:
- whole repo:
npm run validate - single skill while authoring: dev-skill's discipline-aware
validate-skill.js(/dev-skill:validate <path>)
- whole repo:
- Green — fix rule files until the validator reports 0 errors.
- Refactor — tighten wording / dedupe rules, then re-validate to stay green.
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 · 61 lines · 695 tokens per session scan A 43a5c57910a0
dot-skills AGENTS.md is an instructions file published in the GitHub repository pproenca/dot-skills (200 stars, last pushed 17d ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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
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.