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-tool-call)<a href="https://agentmods.dev/commands/maxwellcalkin/sentinel-ai/scan-tool-call"><img src="https://agentmods.dev/badge/commands/maxwellcalkin/sentinel-ai/scan-tool-call/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-tool-call"><img src="https://agentmods.dev/badge/commands/maxwellcalkin/sentinel-ai/scan-tool-call.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.00184 |
| Opus 5 | $0.00000 | $0.00092 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade C, and why
scan-tool-call scanned grade C with 2 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Check for dangerous shell commands (rm -rf, credential access, etc.) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Check for data exfiltration patterns (curl to external servers, etc.) What it actually says
/scan-tool-call — Check if a tool call is safe
Scan a tool call for dangerous operations before execution.
Usage
/scan-tool-call <tool_name>
Behavior
Use the Sentinel AI scan_tool_call MCP tool to:
- Parse the tool name and JSON arguments
- Check for dangerous shell commands (rm -rf, credential access, etc.)
- Check for data exfiltration patterns (curl to external servers, etc.)
- Check for privilege escalation attempts
- Report risk level and whether the call should be blocked
Present findings with:
- Risk level (NONE, LOW, MEDIUM, HIGH, CRITICAL)
- Threat type (dangerous_command, exfiltration, sensitive_file, privilege_escalation)
- Description of the threat
- Whether the tool call would be blocked
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.
- 9d ago First seen · 27 lines · 0 tokens per session scan C 9698d78da93d
scan-tool-call is a command published in the GitHub repository MaxwellCalkin/sentinel-ai (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 184 tokens. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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.