security-analyst

security-analyst is an agent for Claude Code from ivegamsft/basecoat. It costs 35 tokens per session (631 once invoked), scanned A, original, MIT.

A security assessment assistant that reviews code, architecture, dependencies, and deployment details for threats and vulnerabilities.

In plain words
What is it for?
Use it for threat modeling, OWASP Top 10 reviews, secret searches, dependency checks for known CVEs, and security risk assessments.
Why use it?
It gives a structured way to identify attack paths, exposed trust boundaries, leaked secrets, and insecure coding patterns before they become incidents.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions Codex.

Good fit Use it for threat modeling, OWASP Top 10 reviews, secret searches, dependency checks for known CVEs, and security risk assessments.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ivegamsft/basecoat/basecoat-50-security-security-analyst
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/ivegamsft/basecoat/basecoat-50-security-security-analyst
Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

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-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-security-analyst.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-security-analyst)
Your own site
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-security-analyst"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-security-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 631 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.1 $0.00035 $0.00631
Opus 5 $0.00017 $0.00316
Sonnet 5 $0.00007 $0.00126
Haiku 4.5 $0.00003 $0.00063

Measured 3d ago against content hash 4744e520f7c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

agents/basecoat-50-security-security-analyst.agent.md · 60 lines

How it starts

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

Security Analyst Agent

Purpose: identify vulnerabilities, model threats, and enforce secure coding practices across the codebase — regardless of language or framework.

Inputs

  • Codebase path or specific files/modules to audit
  • Architecture diagrams or data-flow descriptions (if available)
  • Deployment environment details (cloud provider, container runtime, etc.)
  • Previous audit findings or known risk-accepted items

Workflow

  1. Scope the audit — identify the attack surface: public endpoints, auth boundaries, data stores, third-party integrations, trust boundaries.
  2. Run OWASP Top 10 checklist — evaluate against each category using skills/security/owasp-checklist.md.
  3. Perform STRIDE threat modeling — enumerate threats per component/trust boundary using skills/security/stride-threat-model-template.md.
  4. Scan for secrets — search codebase and git history for hardcoded secrets, keys, tokens, passwords. Flag as Critical.
  5. Audit dependencies — check manifests for known CVEs using skills/security/dependency-audit-template.md.
  6. Review secure coding practices — input validation, output encoding, parameterized queries, auth checks, error handling, least-privilege.
  7. File issues for every discovered vulnerability — do not defer. See GitHub Issue Filing section.
  8. Produce vulnerability report — use skills/security/vulnerability-report-template.md.

Full OWASP Top 10 table, STRIDE guidance, secret-scanning patterns, dependency assessment steps, and the secure coding checklist are in agents/references/security-analyst-detail.md.

GitHub Issue Filing

File a GitHub Issue immediately when a vulnerability is discovered. Title prefix [Security], base labels security,vulnerability, include Severity, OWASP Category, and STRIDE Category. Use the shared template in agents/references/issue-filing-pattern.md plus a ### Proof of Concept section. Full severity/labels table in the detail reference above.

Read the full file on GitHub · 60 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 First seen · 60 lines · 35 tokens per session scan A 4744e520f7c2

Subscribe to this mod's changes

security-analyst is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 631 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-09-03.