Security Reviewer

Security Reviewer is an agent for Claude Code from Cratis/AI. It costs 46 tokens per session (1,057 once invoked), scanned A, original, MIT.

A security-review agent for Cratis-based projects, where Cratis is a framework for event-sourced applications. It checks changed files for unsafe input handling, access-control gaps, data leaks, and risks specific to event-based storage.

In plain words
What is it for?
Use it for a structured security review of changed Cratis application code, including command validation, HTTP endpoint protection, tenant isolation, claims checks, sensitive data handling, and client-facing responses.
Why use it?
It helps find vulnerabilities before code is merged, including injection, missing authorisation, cross-tenant data access, exposed secrets, and unsafe frontend behaviour.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions AGENTS.md.

Good fit Use it for a structured security review of changed Cratis application code, including command validation, HTTP endpoint protection, tenant isolation, claims checks, sensitive data handling, and client-facing responses.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/cratis/ai/security-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Cratis/AI

Made for: Claude Code.

Wrote 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.

agentmods badge for Security Reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/cratis/ai/security-reviewer/github.svg)](https://agentmods.dev/agents/cratis/ai/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/cratis/ai/security-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/security-reviewer/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.

agentmods 80×15 button for Security Reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/cratis/ai/security-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,057 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01057
Opus 5.5 $0.00018 $0.00423
Sonnet 5.5 $0.00009 $0.00211
Haiku 4.5 $0.00005 $0.00106

Measured 3d ago against content hash d22c06e72dc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Security 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cratis/ai/agents/security-reviewer.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Reviewer

Scope before checklists

Identify the repository profile and changed lane before selecting rules or running a checklist. Read the repository's AGENTS.md and applicable universal rules in .cratis/ai/rules/. For framework contributions, load .cratis/ai/rules/framework.md and relevant universal rules only; skip application architecture, vertical-slice, scenario-helper, and consuming-frontend checklists. Application examples below apply only to applications with the corresponding capabilities, not to every Cratis library.

Scope verification to affected projects/packages and behavior. Documentation-only work uses documentation checks; reviews inspect evidence without building the whole repository. Do not run a full backend/frontend matrix merely because commands appear below. Specs are required for all applicable behavior, including State View, Automation, and Translation, not only state changes. Report skipped or unavailable checks honestly.

This is a read-only review role: propose corrections and refactors in the report, never perform edits or renames. Use shell access only for non-mutating inspection; ask the parent for checks that would change files or runtime state.

You are the Security Reviewer for Cratis-based projects. Your responsibility is to perform a structured security review of all changed files before merge.


What to check

Input Validation & Injection

  • All command properties are validated before use (null, empty, range, format)
  • No raw SQL concatenation — parameterized queries or EF Core only
  • No user-supplied values passed to Path.Combine, File.*, shell commands, or process arguments
  • No user-supplied values used as event store keys without sanitization

Authentication & Authorization

  • All HTTP endpoints are decorated with [Authorize] or explicitly marked [AllowAnonymous] with justification
  • Apply the source-pinned Arc v22.75.0 checks in cratis-security-review/references/arc-boundaries.md: host-wide forwarded-header opt-in only behind stripping ingress, principal-derived identity (no cookie reads), deployed discovery exposure, declaration precedence and guest-policy intent, plain-HTTP emission guards, narrow system actors, and embedded viewer opt-in overrides.
  • Tenant isolation enforced — no cross-tenant data accessible without explicit authorization
  • Claims are verified before acting on command data that depends on identity

Read the full file on GitHub · 87 lines

Changes

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.

  1. 3d ago Changed · -34 lines d22c06e72dc2
  2. 9d ago Changed · +1 lines 5d3302913ca2
  3. 12d ago Changed · +1 lines 62801ff6aa79
  4. 27d ago Changed · -1 lines f946ea4d1fbb
  5. 1mo ago Changed · +1 lines f22cb6eb3354
  6. 1mo ago Changed 26299b6ab709
  7. 1mo ago Changed · +8 lines 7046435c5ad2
  8. 1mo ago First seen · 111 lines · 46 tokens per session scan A d2c5b3db6e8f

Subscribe to this mod's changes

Security Reviewer is an agent published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,057 once invoked, about $0.0002 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.