agentmods.dev

kiro-rails: Command for Claude Code

.claude/commands/review-code-security.md

review-code-security is a command for Claude Code from sourjya/kiro-rails. It costs 44 tokens per session (4,453 once invoked), scanned A, original, MIT.

A tiered application-security review checks code for security problems at different points in development. It covers areas such as exposed secrets, access control, cryptography, common web risks, and third-party dependencies.

In plain words
What is it for?
Use it for staged-file checks before commits, broader reviews after a feature is complete, and end-of-sprint security audits that produce a security review report.
Why use it?
It helps focus reviews on real security risks relevant to the current stage of work. Existing threat models, architecture decisions, and security records can prevent duplicate or irrelevant findings.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is sourjya/kiro-rails's own configuration. It tells Claude Code how to work on kiro-rails itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kiro-rails configures →

not rated 9repo 3mo ago A scan 44 tokens original MIT
View source ↗ sourjya/kiro-rails
Reuse

Borrowing it

Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/commands/review-code-security.md
Clone the repo
git clone --depth 1 https://github.com/sourjya/kiro-rails

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 review-code-security

README.md
[![agentmods](https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-code-security/github.svg)](https://agentmods.dev/commands/sourjya/kiro-rails/review-code-security)
Your own site
<a href="https://agentmods.dev/commands/sourjya/kiro-rails/review-code-security"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-code-security/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 review-code-security

Your own site · 80×15
<a href="https://agentmods.dev/commands/sourjya/kiro-rails/review-code-security"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-code-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 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.00044 $0.04453
Opus 5.5 $0.00018 $0.01781
Sonnet 5.5 $0.00009 $0.00891
Haiku 4.5 $0.00004 $0.00445

Measured 1mo ago against content hash 32fe7e79c41f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-code-security scanned grade A 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 1mo 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.

Unrestricted tool accesslowExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- D5. Lock file integrity - verify `package-lock.json`, `poetry.lock`, or equivalent is committed, consistent with the manifest, and not manually edited; flag `postinstall` or build-time scripts in `package.json` that ex

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- T1-S6. `subprocess` with `shell=True`, `os.system()` calls
.claude/commands/review-code-security.md · 343 lines

How it starts

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

You are a senior application security and code quality auditor performing a comprehensive review. Prioritize real exploitability over generic warnings. Prefer smallest safe remediation.

Before scanning, read these context documents if they exist:

  • docs/security/THREAT_MODEL.md - trust boundaries, what's in/out of scope
  • docs/decisions/ ADRs - architectural decisions that explain intentional patterns
  • docs/security/SECURITY_LOG.md - previously reviewed findings (avoid re-reporting)

Use documented trust boundaries to skip findings on explicitly trusted paths. Do not flag documented exceptions as findings.

This prompt is tier-aware. Each hook invocation will specify which tier to run. Execute only the categories and rules defined for that tier. Do not run categories from higher tiers unless explicitly instructed.

Tier 1 - Pre-Commit (Staged Files Only)

Run when invoked by the pre-commit hook. Scope is staged files only.

Categories

SECRETS & CREDENTIALS

  • T1-S1. Hardcoded secrets: AWS keys (AKIA...), API keys, passwords, tokens, private keys assigned to variables or passed as string literals
  • T1-S2. .env files staged that are not .env.example
  • T1-S3. Private keys or certificates in source files
  • T1-S4. Base64-encoded credentials or secret material embedded in code

UNSAFE EXECUTION

  • T1-S5. eval(), exec(), innerHTML assignment, dangerouslySetInnerHTML without sanitization
  • T1-S6. subprocess with shell=True, os.system() calls
  • T1-S7. Raw SQL string interpolation - not parameterized queries

AUTH & ACCESS

  • T1-S8. Auth or authorization checks bypassed or weakened in auth files, middleware, or route handlers
  • T1-S9. New API endpoints missing auth decorators or guards

INPUT & OUTPUT

  • T1-S10. New FastAPI routes without Pydantic model validation on request bodies
  • T1-S11. Pydantic schemas with string fields missing max_length constraints
  • T1-S12. Raw exception messages or stack traces returned in API responses
  • T1-S13. PII (email, name, address, phone) logged in plain text without masking

Read the full file on GitHub · 343 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. 1mo ago First seen · 343 lines · 44 tokens per session scan A 32fe7e79c41f

Subscribe to this mod's changes

review-code-security is a command published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 4,453 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (unrestricted tool access, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code reviewSecurity
Related

Other commands, from other repositories

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

refactor

Systematic code refactoring with smart scope detection.

RchGrav/claudebox · 9 tokens

init

Install the formatters this repository needs, with every command visible before it runs.

azrtydxb/procoder · 16 tokens

spec-trace-requirements

You are verifying that implementation changes trace back to specification requirements.

rjmurillo/ai-agents · 0 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

boot

Start a new PromptKit prompt assembly session (alias for /bootstrap).

microsoft/PromptKit · 14 tokens