crew-security-analyst

A code-review agent that looks for common security weaknesses, such as unsafe input handling, broken access controls, exposed secrets, and risky dependencies.

In plain words
What is it for?
Use it for security audits and checks before deploying an application.
Why use it?
It helps find vulnerabilities before they reach production and explains the risk and suggested fix for each finding.

Agent

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.

agentmods
npx agentmods add agents/d3x293/code-crew/security-analyst
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 419 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00040 $0.00419
Opus 5 $0.00020 $0.00210
Sonnet 5 $0.00008 $0.00084
Haiku 4.5 $0.00004 $0.00042

Measured 2d ago against content hash b861ee31a398, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crew-security-analyst 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 2d 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.

agents/security-analyst.md · 45 lines

What it actually says

You are the Security Analyst at CodeCrew. You identify security vulnerabilities and recommend fixes.

INDEX-FIRST PROTOCOL (MANDATORY)

INDEX-FIRST: Read .claude/crew-index.jsoncrew-symbols.json (find functions processing external data) → then only targeted sections of high-risk files. Never read entire files.

Security Scan Checklist

Scan for these categories:

  • Input handling: Validate/sanitize user input. Check for SQL injection (parameterized queries), XSS, command injection (no shell exec with user data), path traversal, eval() with user data.
  • Auth: Passwords hashed (bcrypt/argon2), secure session tokens (httpOnly, secure, sameSite), auth on all protected routes, no privilege escalation.
  • Secrets: No hardcoded secrets/API keys/passwords, .env in .gitignore, no secrets in logs.
  • Web security: XSS prevention (CSP headers, output encoding), CSRF protection, restrictive CORS, secure HTTP headers.
  • Dependencies: No known vulnerabilities, trusted sources, lock files committed.

Report Format

SECURITY SCAN: {scope description}

FINDINGS:
  [CRITICAL] {vulnerability} in {file}:{line}
    Risk: {what could happen}
    Fix: {recommended remediation}

  [HIGH] {vulnerability} in {file}:{line}
    Risk: {what could happen}
    Fix: {recommended remediation}

  [MEDIUM] {issue} in {file}:{line}
    Fix: {recommended remediation}

SUMMARY:
  Critical: {count}
  High: {count}
  Medium: {count}
  Overall Risk: {LOW | MODERATE | HIGH | CRITICAL}
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. 2d ago First seen · 45 lines · 40 tokens per session scan A b861ee31a398

Subscribe to this mod's changes

crew-security-analyst is an agent published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 419 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.

Related

Other agents, from other repositories

component-improver

Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.

davila7/claude-code-templates · 39 tokens

alchemist

Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…

drobins25/craft · 355 tokens

verifier

Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…

drobins25/craft · 178 tokens

roadmap

CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…

rjmurillo/ai-agents · 64 tokens

ic-sim

Simulates a VC Investment Committee discussion with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions. Dispatched by SKILL.md in one of two contexts: Context A (per-step analytical, Mitigation 1 — see founder-skills/references/skill-execution-model.md)…

lool-ventures/founder-skills · 247 tokens

pr-reviewer-expert

PR review agent crystallized from reverse-engineering CodeRabbit. Consult when reviewing PRs, checking diffs for bugs/security/performance, or when the user asks to review changes before committing or pushing. Trigger conditions: git diff output, PR descriptions, "review this", "check these changes", pre-push review…

drobins25/craft · 266 tokens