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/robcsaszar/sentinel/agents-mdgit clone --depth 1 https://github.com/robcsaszar/sentinelWhat 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.00168 | $0.00168 |
| Opus 5 | $0.00084 | $0.00084 |
| Sonnet 5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
sentinel 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 yesterday.
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
AGENTS.md
Mission
This repo publishes the sentinel skill: a single skill under skills/sentinel/. There is no build, no tests, no runtime of its own. The deliverable is the contents of that one directory. Changes should be judged by: would a stranger who installs this skill into their own project get a correct, evidence-backed security audit out of it, one that doesn't assume Orakl's codebase, stack, or conventions?
Judgment boundaries
ASK:
- Ask before removing the skill or restructuring its phases; this repo has exactly one skill and no fallback if it regresses.
ALWAYS:
- Don't let the skill's content drift toward assumptions specific to any one codebase or framework; remediation guidance should stay generic enough to adapt to whatever stack the installing project actually uses.
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.
- yesterday First seen · 14 lines · 168 tokens per session scan A 2e2e55f6ba3a
sentinel AGENTS.md is an instructions file published in the GitHub repository robcsaszar/sentinel (0 stars, last pushed 3d ago), licensed MIT. It adds 168 tokens to every session, about $0.0008 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
CheatSheetSeries CLAUDE.md
Claude Code instructions for OWASP/CheatSheetSeries, covering claude.md and for maintainers.
aigis CLAUDE.md
Instructions for killertcell428/aigis, covering aigis — project guidelines, zenn記事管理（zenn cli + github連携）, ディレクトリ構成, 記事の作成 and プレビュー.
agents-shipgate CLAUDE.md
Instructions for ThreeMoonsLab/agents-shipgate, covering claude code instructions, running the cli in this repository, permissions, output handling and slash command.
plamen CLAUDE.md
Instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.
digital-innovation-agents GEMINI.md
Instructions for pssah4/digital-innovation-agents, a project described as: Digital Innovation Agents is an AI-augmented workflow that connects business analysis and software engineering in one consistent skill set.
rubydex AGENTS.md
AGENTS.md instructions for Shopify/rubydex, covering instructions, project overview, documentation, ruby gem and structure.