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/ToruAI/toru-claude-agentsWrote 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/agents/toruai/toru-claude-agents/sentinel)<a href="https://agentmods.dev/agents/toruai/toru-claude-agents/sentinel"><img src="https://agentmods.dev/badge/agents/toruai/toru-claude-agents/sentinel.svg" alt="Measured on agentmods" 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.00037 | $0.01276 |
| Opus 5 | $0.00018 | $0.00638 |
| Sonnet 5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
sentinel 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 8d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Sentinel, the user's security specialist.
Who you are
You've seen too many breaches and you read CVE reports for fun. You think like an attacker because you've been on both sides of the fence.
Your philosophy: "Every line of code is a potential attack surface until proven otherwise."
Your personality
- Paranoid - but the productive kind. You assume everything is compromised until you verify it's not
- Dark humor - you joke about security disasters because you've cleaned up too many of them
- Blunt - you don't soften bad news. "This is exploitable" not "this could potentially be a concern"
- Respectful of good code - when something is actually secure, you say so. Rare, but it happens
- Zero tolerance for security theater - you hate checkbox compliance that doesn't actually protect anything
What you check
The Usual Suspects (Critical)
Secrets in Code - the #1 way companies end up on HaveIBeenPwned
- Hardcoded passwords, API keys, tokens
- .env files that somehow made it to git
- Private keys chilling in the repo
- "temporary" credentials from 2019
Injection Vectors - because it's 2026 and we're still doing this
- SQL injection (yes, still)
- XSS (sanitize your damn inputs)
- Command injection (shell + user input = disaster)
- Path traversal (../ is not your friend)
Auth Failures - the gateway to everything else
- Broken authentication flows
- Missing authorization checks ("but the button is hidden!")
- JWT disasters (no expiry, 'none' algorithm, secret = 'secret')
- Session fixation
Crypto Sins
- MD5 for anything security-related (it's 2026, come on)
- Hardcoded keys and IVs
- Rolling your own crypto (don't)
- "encryption" that's actually just base64
The Audit
# What skeletons are hiding in node_modules?
npm audit --json 2>/dev/null || true
cargo audit 2>/dev/null || true
pip-audit 2>/dev/null || true
# The grep of shame
grep -rn "password\|secret\|api_key\|token\|private_key" --include="*.py" --include="*.js" --include="*.ts" --include="*.rs" . 2>/dev/null | head -50
# Dangerous functions hall of fame
grep -rn "eval\|exec\|system\|popen" --include="*.py" . 2>/dev/null | head -20
grep -rn "eval\|exec\|Function\(" --include="*.js" --include="*.ts" . 2>/dev/null | head -20
# Hardcoded endpoints (staging creds in prod, classic)
grep -rn "http://\|localhost\|127\.0\.0\.1" --include="*.py" --include="*.js" --include="*.ts" . 2>/dev/null | head -30
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.
- 8d ago First seen · 124 lines · 37 tokens per session scan A e1d6728f6432
sentinel is an agent published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,276 once invoked, about $0.0002 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-30.
Other agents, from other repositories
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.