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 skills/cratis/verticalslices/review-securitynpx skills add Cratis/VerticalSlices --skill review-securitygit clone --depth 1 https://github.com/Cratis/VerticalSlicesWrote 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/skills/cratis/verticalslices/review-security)<a href="https://agentmods.dev/skills/cratis/verticalslices/review-security"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/review-security.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 | $0.00045 | $0.00537 |
| Opus 5 | $0.00023 | $0.00269 |
| Sonnet 5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
review-security 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 5d 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.
This is a copy
100% identical to review-security — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perform a structured security review of changed code.
Input Validation & Injection
- All command properties 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 args - No user-supplied values used as event-store keys without sanitization
Authentication & Authorization
- All HTTP endpoints decorated with
[Authorize]or explicitly[AllowAnonymous]with justification - Tenant isolation enforced — no cross-tenant data accessible without authorization
- Claims verified before acting on identity-dependent command data
Sensitive Data Exposure
- No passwords, secrets, API keys, or tokens stored in event properties or read models
- No PII returned to clients that did not provide it
- Query results scoped to requesting tenant/user — never return all-tenant data
Secrets & Configuration
- No secrets in source code, config files, or test fixtures
- Secrets loaded from environment variables or a secrets manager
- No hard-coded connection strings in non-test code
Event Sourcing Specifics
- Events are immutable records — no mutable state in the event store
- Aggregate/event-store IDs generated server-side, never accepted from untrusted clients
- Event upcasting logic does not allow injection of unexpected properties
- Uniqueness constraints cannot be bypassed by concurrent multi-tenant writes
Frontend
- No user-supplied values in
dangerouslySetInnerHTML - No tokens or secrets in
localStorage— usehttpOnlycookies or in-memory state - Command DTOs contain only the minimum required fields
- No client-side access control not also enforced server-side
Risk classification
- 🔴 Critical — must fix before merge
- 🟡 Medium — should fix soon
- 🟢 Low — fix when convenient
Output format
Start with: Security Review: ✅ No issues / ⚠️ Low-risk findings / ❌ Blocking issues found
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.
- 5d ago First seen · 58 lines · 45 tokens per session scan A bb8e4a571f28
review-security is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 537 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-security, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
cratis-command
Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…
ship-changes
Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, prepare no-effect dispositions for related issues, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or…
cratis-react-page
Step-by-step guidance for building a React page in a Cratis Arc application — DataPage lists, CommandDialog toolbar actions, confirmation and busy-indicator dialogs, row selection, details components, observable queries, and MVVM. Use when building or modifying a page that lists/displays data, adding a table, wiring…
cratis-readmodel
Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…
toolbar
Use this skill when asked to add or build a canvas-style icon toolbar using the @cratis/components Toolbar component. Covers Toolbar, ToolbarButton, ToolbarSeparator, ToolbarSection, ToolbarContext, and ToolbarFanOutItem. Use whenever building tool panels, drawing tool selectors, zoom controls, or any icon-button…
add-traces
Use this skill when asked to add OpenTelemetry tracing to a class in a Cratis Chronicle Kernel project. Produces Traces.cs companion files using the [Span] source-generator pattern from Cratis.Traces, registers IActivitySource as a keyed DI service, and injects it into the target class.