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/tomimor/skills/agents-mdgit clone --depth 1 https://github.com/tomimor/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/tomimor/skills/agents-md)<a href="https://agentmods.dev/instructions/tomimor/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/tomimor/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.01453 | $0.01453 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
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 3d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working in this repo.
Repo structure
skills/
├── skills/ # All discoverable skills (own + vendor symlinks)
│ ├── miguel-review/ # Own skill (regular directory)
│ ├── impeccable -> ../vendor/impeccable/.claude/skills/impeccable # Vendor symlink
│ └── ...
├── vendor/ # Third-party skill repos (git submodules)
│ └── impeccable/ # pbakaus/impeccable
├── install.sh # Install script with vendor support
├── README.md
└── AGENTS.md # This file
~/.cursor/skills is a symlink to skills/. ~/.claude/skills is a real directory whose entries are per-skill symlinks back into skills/ -- Claude Code does not load skills from a symlinked top-level directory, so the per-skill symlinks are how it picks them up while live edits in this repo still take effect. Any skill directory (or symlink) inside skills/ with a SKILL.md is automatically available to agents in both Cursor and Claude Code.
Re-create the per-skill symlinks if anything drifts:
./install.sh --symlink --all --force --target ~/.claude/skills
Adding a new own skill
Own skills are skills you write and maintain yourself. They live as regular directories under skills/.
- Create the directory and SKILL.md:
skills/<skill-name>/
├── SKILL.md # Required
├── references/ # Optional -- detailed docs the agent reads on demand
│ └── some-reference.md
└── examples.md # Optional
- SKILL.md must have YAML frontmatter with
nameanddescription:
---
name: my-skill-name
description: >-
What this skill does and when to use it. Include trigger phrases
so the agent knows when to activate it. Use when the user mentions
X, Y, or Z.
---
- Register the skill in
install.shby adding an entry to theSKILLSarray:
SKILLS=(
...existing entries...
"my-skill-name:Short description for the install picker"
)
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.
- 3d ago First seen · 144 lines · 1,453 tokens per session scan A fd0eb14f90f6
skills AGENTS.md is an instructions file published in the GitHub repository tomimor/skills (2 stars, last pushed 16d ago), licensed MIT. It adds 1,453 tokens to every session, about $0.0073 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
agents AGENTS.md
Instructions for astronomer/agents, covering claude code plugin development, plugin structure, installing the plugin, add the marketplace (from repo root) and install the plugin.
agentregistry copilot-instructions.md
Instructions for agentregistry-dev/agentregistry, covering github copilot instructions and keeping the pr description up-to-date.
loom CLAUDE.md
Claude Code instructions for cosmix/loom, covering claude.md, project overview, build commands, architecture and source layout (loom/src/).
copilot AGENTS.md
Instructions for navikt/copilot, covering agents.md for navikt/copilot, what this repo is, efficiency rule, standard commands and conventions.
autovault CLAUDE.md
Instructions for autoworks-ai/autovault, covering claude.md, project, common commands, architecture and request flow.
skilly AGENTS.md
AGENTS.md instructions for xelandernt/skilly, covering agents.md, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.