Borrowing it
Nothing to install: this file belongs to robcsaszar/sentinel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robcsaszar/sentinel/main/AGENTS.mdgit clone --depth 1 https://github.com/robcsaszar/sentinelWrote 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/robcsaszar/sentinel/agents-md)<a href="https://agentmods.dev/instructions/robcsaszar/sentinel/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/sentinel/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/robcsaszar/sentinel/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/sentinel/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00586 | $0.00586 |
| Opus 5.5 | $0.00234 | $0.00234 |
| Sonnet 5.5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Releasing
Releases are cut by the Release workflow (.github/workflows/release.yml), never by hand. It is a manual workflow_dispatch with one input, tag, and it releases the commit at the tip of the branch it is run on. Run it on main.
The workflow, in order:
- Rejects a tag that is not
vX.Y.Z, or that already exists. - Fails unless
versionin.claude-plugin/plugin.jsonandplugins[0].versionin.claude-plugin/marketplace.jsonboth equalX.Y.Z. - Takes the
## [X.Y.Z]block fromCHANGELOG.mdas the release notes, and fails if there is none. - Creates the tag at the checked-out commit and publishes the GitHub release with those notes.
Nothing is created until every check passes, so a failed run leaves nothing to clean up.
To prepare a release, in one PR:
- Set the same new version in
.claude-plugin/plugin.jsonand.claude-plugin/marketplace.json. - Add a
## [X.Y.Z] - YYYY-MM-DDblock at the top ofCHANGELOG.md, and its[X.Y.Z]: …link reference at the bottom. - Merge to
main.
Then run the workflow on main with tag=vX.Y.Z, from the Actions tab (Release → Run workflow) or from a shell:
gh workflow run release.yml --ref main -f tag=vX.Y.Z
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.
- 1mo ago Changed · +29 lines · +418 tokens per session 8a9bdffb3608
- 1mo ago 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 1mo ago), licensed MIT. It adds 586 tokens to every session, about $0.0023 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.