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/jdrhyne/agent-skills/agents-mdgit clone --depth 1 https://github.com/jdrhyne/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/jdrhyne/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/jdrhyne/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/jdrhyne/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.1 | $0.00603 | $0.00603 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working on this repository.
Repository Structure
agent-skills/
├── skills/ # Skills with tooling, scripts, or workflows
├── prompts/ # Pure instruction prompts (text only)
├── clawdbot/ # Clawdbot-specific skills
├── scripts/ # Repo maintenance scripts
├── README.md # Main documentation (auto-generated sections)
└── AGENTS.md # This file
Adding Content
Adding a Skill (with tooling)
-
Create folder in
/skills:mkdir -p skills/my-skill -
Create
SKILL.mdwith frontmatter:--- name: my-skill description: What this skill does --- # My Skill Instructions, scripts, templates... -
Add supporting files:
scripts/— Helper scriptstemplates/— Template filesexamples/— Example inputs/outputs
Adding a Prompt (pure guidance)
-
Create folder in
/prompts:mkdir -p prompts/my-prompt -
Create
SKILL.mdwith frontmatter:--- name: my-prompt description: Guidance for X --- # My Prompt Instructions and guidelines...
Prompts should be self-contained — no external dependencies or scripts.
Adding Clawdbot Skills
Same as skills, but in /clawdbot:
mkdir -p clawdbot/my-clawdbot-skill
SKILL.md Requirements
Required frontmatter:
name: Identifier (lowercase, hyphens)description: One-line description
Good SKILL.md structure:
- Quick usage examples at the top
- Detailed instructions
- Edge cases / troubleshooting
- References to supporting files
Validation
Before committing:
./scripts/validate-skills.sh
Sync Rule (Required)
If you add or update a skill locally, you must also:
- Add/update the corresponding skill folder in this repo
- Update the README skill list (Skills + Clawdbot-specific)
- Run
./scripts/validate-skills.sh - Open a draft PR with a clear What/Why/How/Testing description
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.
- 6d ago First seen · 107 lines · 603 tokens per session scan A f125b6a43890
agent-skills AGENTS.md is an instructions file published in the GitHub repository jdrhyne/agent-skills (241 stars, last pushed 7d ago), licensed MIT. It adds 603 tokens to every session, about $0.0030 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
read-no-evil-mcp AGENTS.md
Instructions for thekie/read-no-evil-mcp, covering agents.md, project overview, tech stack, development setup and code style.
openbotx AGENTS.md
Instructions for openbotx/openbotx, covering agents.md, build and run, setup (first time), run backend (dev mode with reload) and run frontend (dev mode, separate terminal).
read-no-evil-mcp CLAUDE.md
Instructions for thekie/read-no-evil-mcp, a project described as: A secure email gateway MCP server that protects AI agents from prompt injection attacks hidden in emails.
read-no-evil-mcp GEMINI.md
Instructions for thekie/read-no-evil-mcp, a project described as: A secure email gateway MCP server that protects AI agents from prompt injection attacks hidden in emails.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
Browser4 CLAUDE.md
Claude Code instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.