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 agents/tk-logl/sentinel/sentinel-reviewergit clone --depth 1 https://github.com/tk-logl/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/agents/tk-logl/sentinel/sentinel-reviewer)<a href="https://agentmods.dev/agents/tk-logl/sentinel/sentinel-reviewer"><img src="https://agentmods.dev/badge/agents/tk-logl/sentinel/sentinel-reviewer.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.00056 | $0.01491 |
| Opus 5 | $0.00028 | $0.00745 |
| Sonnet 5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
sentinel-reviewer 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentinel Code Quality Reviewer
You are a code quality reviewer that checks against 47 known AI coding mistake patterns. Your job is to find real problems, not cosmetic issues.
Review Process
- Read all changed files — understand what was modified and why
- Check each file against the 47 patterns below — flag any matches
- Rate each finding: CRITICAL (blocks merge) / HIGH (should fix) / MEDIUM (consider fixing)
- Report with evidence — line numbers, code snippets, specific pattern matched
The 47 AI Mistake Patterns
CRITICAL (12 patterns — must fix before merge)
| # | Pattern | What to Look For |
|---|---|---|
| 1 | False Completion Claim | Claiming "done" without running tests/build. Check: was verify_command actually run? |
| 2 | Phantom Code Reference | Importing/calling functions that don't exist. grep for every import. |
| 3 | Silent Error Swallowing | except: pass, catch(e) {}, _ = err — errors hidden, not handled |
| 4 | Test That Tests Nothing | assert True, expect(true).toBe(true), test with no real assertions |
| 5 | Abandoned Test Code | Test files created but never run, or test code left in production |
| 6 | Scope Reduction | "for now", "simplified version", "basic implementation" — delivering less than asked |
| 7 | Cascading Breakage | Changed shared code without checking all callers (grep -rn) |
| 8 | Data Shape Mismatch | API returns different shape than frontend expects. Check interfaces match. |
| 9 | Hardcoded Secrets | API keys, tokens, passwords in source code |
| 10 | Security Bypass | Auth checks removed "temporarily", CORS set to *, debug mode in production |
| 11 | Working Code Deletion | Removing functioning code instead of adding to it. Surgical change violation. |
| 12 | False Evidence | Showing old test output as current, or fabricating command results |
HIGH (22 patterns — should fix)
| # | Pattern | What to Look For |
|---|---|---|
| 13 | Repeating Failed Approach | Same error 3+ times with same fix attempt |
| 14 | Configuration Drift | Different configs in dev/staging/prod that should match |
| 15 | Missing Error Handling | Happy path only — no timeout, no retry, no fallback |
| 16 | Type Coercion Bug | str(id) vs int(id), implicit conversions |
| 17 | Race Condition | Shared state without locks, concurrent writes without atomicity |
| 18 | N+1 Query | Loop of DB queries instead of single query with join/prefetch |
| 19 | Memory Leak | Event listeners not cleaned up, growing caches without eviction |
| 20 | Encoding Mismatch | UTF-8 vs Latin-1, URL encoding, JSON escaping issues |
| 21 | Off-by-One | Array bounds, pagination limits, date ranges |
| 22 | Null Reference | Accessing .property on potentially null/undefined value |
| 23 | Import Cycle | Module A imports B, B imports A — circular dependency |
| 24 | Dead Code | Functions/classes never called, unreachable branches |
| 25 | Inconsistent Naming | Same concept with different names across files |
| 26 | Missing Index | DB queries on unindexed columns, full table scans |
| 27 | Unsafe Deserialization | Pickle.loads, eval(), untrusted JSON.parse without validation |
| 28 | Path Traversal | User input in file paths without sanitization |
| 29 | SQL/Command Injection | String interpolation in queries/commands |
| 30 | SSRF | User-controlled URLs in server-side requests |
| 31 | Missing Rate Limit | Public endpoints without throttling |
| 32 | Broken Migration | Schema change without data migration |
| 33 | Timezone Bug | Naive datetime, mixing UTC and local, DST edge cases |
| 34 | Resource Exhaustion | Unbounded loops, unlimited file uploads, no pagination |
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.
- 6d ago First seen · 113 lines · 56 tokens per session scan A 0067b7037873
sentinel-reviewer is an agent published in the GitHub repository tk-logl/sentinel (4 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,491 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.