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.
git clone --depth 1 https://github.com/MaxwellCalkin/sentinel-aiWrote 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/commands/maxwellcalkin/sentinel-ai/scan)<a href="https://agentmods.dev/commands/maxwellcalkin/sentinel-ai/scan"><img src="https://agentmods.dev/badge/commands/maxwellcalkin/sentinel-ai/scan/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/commands/maxwellcalkin/sentinel-ai/scan"><img src="https://agentmods.dev/badge/commands/maxwellcalkin/sentinel-ai/scan.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.00000 | $0.00142 |
| Opus 5.5 | $0.00000 | $0.00057 |
| Sonnet 5.5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
scan 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.
What it actually says
/scan — Scan text for safety issues
Scan the provided text for safety issues using all Sentinel AI scanners.
Usage
/scan
Behavior
Run all 7 Sentinel AI safety scanners against the provided text:
- Prompt injection detection
- PII detection and redaction
- Harmful content filtering
- Hallucination signal detection
- Toxicity detection
- Blocked terms checking
- Tool-use safety analysis
Report findings with risk levels (NONE, LOW, MEDIUM, HIGH, CRITICAL) and whether the content should be blocked.
If PII is detected, also show the redacted version of the text.
Input
$ARGUMENTS
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 First seen · 27 lines · 0 tokens per session scan A f0e32175de42
scan is a command published in the GitHub repository MaxwellCalkin/sentinel-ai (25 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 142 tokens. 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 commands, from other repositories
capture-feedback
Quick feedback capture with structured signals.
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
show-lessons
Display promoted lessons and their corrective actions.
staleness-check
Check what governance artifacts went stale based on what was edited this session.
check-drift
Run schema drift detection — compare the live Postgres schema against ORM table definitions, backend function .select() calls, the schema doc, and the techstack inventory.
start
A Korean-language start command for beginning a repair loop after refining a goal, making a backup, giving guidance, and confirming the plan.