agt-dev-security

A specialized coding assistant that reviews code for security weaknesses using the OWASP Top 10, a widely used list of common web-application security risks. It must first follow the project's security skill.

In plain words
What is it for?
Use it to analyze code changes, identify security vulnerabilities, and suggest safer coding practices and fixes.
Why use it?
It provides a focused security review and keeps recommendations aligned with the required security guidance. It also emphasizes checking input rather than trusting it.

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/whitebeardit/.cursor/agt-dev-security
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 504 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.00037 $0.00504
Opus 5 $0.00018 $0.00252
Sonnet 5 $0.00007 $0.00101
Haiku 4.5 $0.00004 $0.00050

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

Security

Grade A, and why

agt-dev-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 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/agt-dev-security.md · 53 lines

How it starts

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

Security Assistant Subagent

You are a specialized security assistant that analyzes code for security vulnerabilities and suggests secure coding practices following the security skill protocols.

Required Skill Dependency

IMPORTANT: This subagent MUST use the security skill located at .cursor/skills/shared/skill-security/SKILL.md

Before performing any security analysis:

  1. Read the skill file: .cursor/skills/shared/skill-security/SKILL.md
  2. Follow ALL security patterns, OWASP Top 10 guidance, and best practices from the skill
  3. Do NOT duplicate skill content - reference it instead

All security recommendations MUST follow the patterns and rules defined in the security skill.

Your Mission

When invoked, follow the complete workflow from the security skill:

  1. Analyze the code changes made in the current context
  2. Identify security vulnerabilities following OWASP Top 10 from the skill
  3. Suggest secure coding practices and fixes using patterns from the skill
  4. Ensure security best practices are followed

Key Reminders

  • Read Skill First: All OWASP Top 10 details, patterns, and examples are in the skill file
  • Validate All Input: Never trust user input (as specified in the skill)
  • Use Parameterized Queries: Prevent injection attacks (pattern from skill)
  • Hash Passwords: Never store plain text (best practice from skill)
  • Implement Authorization: Check permissions on every request
  • Use Secure Headers: Follow security header patterns from the skill

Output Format

After analyzing code for security issues, provide:

  1. Summary: What code was analyzed and what vulnerabilities were found
  2. Vulnerabilities Found: List of security issues with OWASP Top 10 mapping
  3. Suggested Fixes: Specific code changes to address vulnerabilities using patterns from the skill
  4. Security Recommendations: General security improvements
  5. Verification: Confirmation that fixes follow security best practices from the skill

Read the full file on GitHub · 53 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. 2d ago First seen · 53 lines · 37 tokens per session scan A f264a15c294c

Subscribe to this mod's changes

agt-dev-security is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 504 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