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/olanokhin/agent-security-skill/agents-mdgit clone --depth 1 https://github.com/olanokhin/agent-security-skillWhat 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.00140 | $0.00140 |
| Opus 5 | $0.00070 | $0.00070 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
agent-security-skill 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.
What it actually says
Agent Security Skill
Load and follow AI_SECURITY.md from the project root (also referenced as @AI_SECURITY.md in CLAUDE.md-style imports — if your agent does not support @-imports, read the file directly).
When the user says owasp my code, owasp this, owasp this PR, or ai security review, audit the current file, diff, branch, or PR against:
LLM01-LLM10PIPE01-PIPE13ASI01-ASI10
Report CRITICAL and HIGH findings first with file/line location, issue, and fix.
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 · 12 lines · 140 tokens per session scan A 4b231efd272b
agent-security-skill AGENTS.md is an instructions file published in the GitHub repository olanokhin/agent-security-skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 140 tokens to every session, about $0.0007 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
stride-gpt AGENTS.md
Instructions for mrwadams/stride-gpt, covering agents.md, what this project is, repository layout, how the agentic analysis works and progressive disclosure pattern.
prismor CLAUDE.md
Instructions for PrismorSec/prismor, covering prismor security — claude.md, prismor runtime protection, cloaking (secret prevention) and working in this repo.
skill-validator CLAUDE.md
Instructions for raphaelstolt/skill-validator, covering skill-validator, project info, common commands, code conventions and architecture.
bdb-dev-optimized-agent-skills CLAUDE.md
Instructions for hybridlabor-api/bdb-dev-optimized-agent-skills, covering bdb agent skills — global instructions, docs & pipeline, how many agents, safety gate — mechanically enforced, not advisory and non-negotiable.
mitre-mcp AGENTS.md
Instructions for lidless-labs/mitre-mcp, covering repository guidance, definition of done, project shape, verification workflow and soc safety (hard prohibitions).
saas-cybersecurity AGENTS.md
Instructions for YankielDBC2/saas-cybersecurity, covering agent working agreement, purpose, rules, repository map and definition of done.