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/practicalswan/agent-skills/agents-mdgit clone --depth 1 https://github.com/PracticalSwan/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/practicalswan/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/practicalswan/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/practicalswan/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.04068 | $0.04068 |
| Opus 5 | $0.02034 | $0.02034 |
| Sonnet 5 | $0.00814 | $0.00814 |
| Haiku 4.5 | $0.00407 | $0.00407 |
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 today.
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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository contains shared skills for GitHub Copilot, Claude Code, and
Codex, and this file defines the workspace-specific rules that should
apply to any AI agent operating in C:\Users\LOQ\.copilot\skills.
Required Session Start Rule
- Every new session in this workspace must begin by reading
LESSON.md. - Treat
LESSON.mdas required startup context before analysis, planning, edits, validation, reviews, or advisory work. - If
LESSON.mdis missing or unreadable, stop and report that blocker before continuing.
Required Completion, Sync, And Publish Rule
- For every user-requested mutation task in this workspace, complete the
requested work in
C:\Users\LOQ\.copilot\skillsfirst. - After the work is complete, run the repo validation, then sync outward to the downstream skill folders every time.
- If the AI agent judges the result satisfactory, commit and push to GitHub without asking for another confirmation.
- Treat work as satisfactory only when validation passes, sync completes, the task is complete, no requested step was skipped, no required command was rejected, no unresolved secret/security/privacy issue remains, and the final diff matches the user's request.
- Elevate to the user before commit or push when there are security concerns, incomplete work, skipped steps, rejected or blocked required commands, validation/sync failures, unexpected unrelated dirty files that make staging unsafe, or any other reason the work is not satisfactory.
- For read-only or advisory tasks with no file changes, do not create empty sync, commit, or push churn; report that no mutation workflow was needed.
Workspace Role
- Main branch:
C:\Users\LOQ\.copilot\skills - New maintained skills must be added or imported here first.
- Maintained skills live here and are synced outward to downstream targets.
- Copied official superpowers are tracked here for discovery and cross-client sync, but they are not maintained the same way as the catalog's maintained skills.
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.
- today Changed · +12 lines · +156 tokens per session da65b10a8b27
- 4d ago First seen · 355 lines · 3,912 tokens per session scan A 2bc1ae6215cc
agent-skills AGENTS.md is an instructions file published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed 3d ago), licensed MIT. It adds 4,068 tokens to every session, about $0.0203 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.