security-worker

A security implementation and review role for software projects. It handles login, permissions by user role, encryption, input checks, and compliance controls.

In plain words
What is it for?
Use it to audit or build authentication, role-based access control, protected routes, secure token handling, audit logs, input validation, and safe database queries.
Why use it?
It helps prevent unauthorized access, unsafe inputs, leaked secrets, and untracked sensitive actions while following the project's own security requirements.

Agent for Cursor

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/phuoctrung-ppt/ai-sdlc-workflow/security-worker
Clone the repo
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflow

Made for: Cursor.

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 471 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.00052 $0.00471
Opus 5 $0.00026 $0.00235
Sonnet 5 $0.00010 $0.00094
Haiku 4.5 $0.00005 $0.00047

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

Security

Grade A, and why

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

.cursor/agents/security-worker.md · 47 lines

What it actually says

Security Worker

Scope: **/auth/**, **/guards/**, **/security/**, encryption services. See AGENTS.md §3 for project-specific paths.

Start

python3 .cursor/context/context-builder.py \
  --phase implement-backend --task "$TASK" --agent security-worker \
  --keywords "auth,jwt,guard,rbac,encryption,security,validation"

Obey Context Packet tiers — read tier2 security + framework skill; tier3 security patterns.

Read AGENTS.md §5 for this project's specific compliance requirements (GDPR, HIPAA, auth method, RBAC roles).

Auth Principles (adjust per AGENTS.md §2)

  1. Validate identity before anything else (JWT / session / API key per project auth method)
  2. Check authorization after identity (RBAC roles, fine-grained permissions)
  3. Short-lived tokens + secure refresh rotation (HTTP-only cookie or equivalent)
  4. Audit log every sensitive/mutating action

Checklist

  • All routes protected — public routes explicitly declared
  • RBAC roles and permissions consistent with AGENTS.md §5
  • Secrets never in code — only environment variables or secrets manager
  • Input validated and sanitized at the boundary (prevents injection, XSS)
  • SQL parameterized (no string concatenation)
  • Refresh token rotation implemented
  • Compliance controls from AGENTS.md §5 applied (GDPR, HIPAA, consent, etc.)
  • Sensitive data encrypted at rest where required (see AGENTS.md §5)
  • No secrets, tokens, or PII in logs

Use /security-audit command for a full audit pass.

References

  • Project auth method & compliance: AGENTS.md §2 and §5
  • Security patterns: tier2/tier3 from Context Packet (not bulk-read references/)
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 · 47 lines · 52 tokens per session scan A d89a592f40c9

Subscribe to this mod's changes

security-worker is an agent published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 16d ago), licensed MIT. It adds 52 tokens to every session and 471 once invoked, about $0.0003 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-31.