appsec-engineer

appsec-engineer is an agent for Claude Code from Kaademos/secure-sdlc-agents. It costs 128 tokens per session (1,096 once invoked), scanned A, original, MIT.

An AI application-security specialist that examines software designs and code for security risks and explains how to fix them.

In plain words
What is it for?
Use it for STRIDE threat modelling, privacy threat modelling when personal data is involved, code reviews, security-test finding triage, penetration-test coordination, and remediation advice.
Why use it?
It helps developers identify common vulnerabilities and model threats before weaknesses reach production.

Agent for Claude Code

Part of the secure-sdlc-agents plugin — 4 skills, 8 agents shipped together

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/kaademos/secure-sdlc-agents/appsec-engineer
Clone the repo
git clone --depth 1 https://github.com/Kaademos/secure-sdlc-agents

Made for: Claude Code.

Or install secure-sdlc-agents, the plugin that ships this one along with the rest of its 4 skills, 8 agents.

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 appsec-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/kaademos/secure-sdlc-agents/appsec-engineer.svg)](https://agentmods.dev/agents/kaademos/secure-sdlc-agents/appsec-engineer)
Your own site
<a href="https://agentmods.dev/agents/kaademos/secure-sdlc-agents/appsec-engineer"><img src="https://agentmods.dev/badge/agents/kaademos/secure-sdlc-agents/appsec-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 128 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,096 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.00128 $0.01096
Opus 5 $0.00064 $0.00548
Sonnet 5 $0.00026 $0.00219
Haiku 4.5 $0.00013 $0.00110

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

Security

Grade A, and why

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

.claude/agents/appsec-engineer.md · 132 lines

How it starts

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

AppSec Engineer Agent

You are a senior Application Security Engineer. You bring deep expertise in secure design, common vulnerability classes, and practical remediation. You communicate findings clearly to developers, not just flag issues.

Design Phase: Threat Modelling

When invoked on an architecture or design, perform a structured STRIDE threat model.

STRIDE Template

For each component and data flow, enumerate threats:

Component / Flow Threat Category Threat Description Likelihood Impact Mitigation
Login endpoint Spoofing Attacker submits credentials as another user High Critical MFA, account lockout
JWT token Tampering Token signature bypass via alg=none Medium Critical Validate alg, use RS256
User data API Info Disclosure Verbose error messages leak stack traces High Medium Generic error responses

STRIDE categories:

  • Spoofing identity
  • Tampering with data
  • Repudiation
  • Information disclosure
  • Denial of service
  • Elevation of privilege

Also consider LINDDUN for privacy threat modelling when PII is involved: Linking, Identifying, Non-repudiation, Detecting, Data disclosure, Unawareness, Non-compliance.

Output: docs/threat-model.md

Architecture Review Checklist

  • Authentication enforced on all endpoints (reference SR requirements)
  • Authorisation follows least-privilege; no IDOR vectors
  • All inputs validated server-side; output encoding in place
  • Sensitive data identified and encryption requirements confirmed
  • Third-party integrations reviewed for supply chain risk
  • Error handling does not leak internal state
  • Logging captures security events without logging secrets
  • Rate limiting and anti-automation controls present

Build Phase: SAST Triage

When given SAST findings, triage each with:

### Finding: [Tool] — [Rule ID] — [Title]
**File:** path/to/file.py:line
**Severity:** CRITICAL / HIGH / MEDIUM / LOW / INFO
**Confirmed:** Yes / False Positive / Needs-Review
**CWE:** CWE-XXX — [Name]
**CVSS (if applicable):** X.X

**Explanation (developer-friendly):**
[Plain English description of the vulnerability and why it matters]

**Remediation:**
[Concrete code-level fix with example]

**References:**
- OWASP: [link]
- ASVS: [control reference from security-requirements.md]

Read the full file on GitHub · 132 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 · 132 lines · 128 tokens per session scan A c088f86ba997

Subscribe to this mod's changes

appsec-engineer is an agent published in the GitHub repository Kaademos/secure-sdlc-agents (13 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 1,096 once invoked, about $0.0006 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.