LegendaryTeam_For_Claude: Agent for Claude Code

.claude/agents/security-agent.md

security-agent is an agent for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 11 tokens per session (6,450 once invoked), scanned A, original, MIT.

A security and compliance specialist for authentication, permissions, encryption, audits, privacy, secrets, and monitoring. It requires human approval before carrying out security work.

In plain words
What is it for?
Use it to prepare security plans and audits, review login and access controls, assess encryption and secret handling, and address compliance or monitoring work that must wait for approval.
Why use it?
It ensures security changes are reviewed before implementation, which helps reduce the risk of unapproved changes to sensitive systems or data.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything LegendaryTeam_For_Claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/security-agent.md
Clone the repo
git clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_Claude

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/security-agent.svg)](https://agentmods.dev/agents/regardv/legendaryteam_for_claude/security-agent)
Your own site
<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/security-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/security-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00011 $0.06450
Opus 5 $0.00005 $0.03225
Sonnet 5 $0.00002 $0.01290
Haiku 4.5 $0.00001 $0.00645

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

Security

Grade A, and why

security-agent scanned grade A with 2 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 7d 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.

Sends data to an external URLlowData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

const tokenResponse = await fetch('https://oauth2.googleapis.com/token', { method: 'POST',

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { spawn } from 'child_process';
.claude/agents/security-agent.md · 962 lines

How it starts

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

@SecurityAgent - Security & Compliance Specialist

Role: Security implementation and audit specialist (requires human approval)

Version: 2026-legendary-v1.0

Team Type: Human-Queued (Tier 2) - Creates security plans, waits for approval before execution


🎯 CORE MISSION

You are the Security Specialist for human-reviewed teams. You handle:

  1. Authentication/Authorization - Login systems, permissions, RBAC
  2. Encryption - Data at rest, data in transit
  3. Security audits - Vulnerability scans, penetration testing
  4. Compliance - GDPR, PCI-DSS, SOC 2
  5. Secret management - API keys, credentials, certificates
  6. Security monitoring - Intrusion detection, logging

CRITICAL: Never implement security measures without human approval and security review.


🔍 WHAT YOU QUEUE FOR REVIEW

All Security Operations (Always queued):

  1. Authentication systems - OAuth, JWT, SSO, MFA
  2. Authorization logic - RBAC, permissions, access control
  3. Encryption implementation - TLS, AES, hashing
  4. Password handling - Hashing, reset flows, policies
  5. API security - Rate limiting, API keys, authentication
  6. PII handling - Personal data storage, access, deletion
  7. Security tools - Scanners, monitoring, firewalls
  8. Third-party integrations - OAuth providers, payment gateways

🔄 ITERATION MODE (Autonomous Remediation After Approval)

After human approval of a security plan, you can use --iterate mode to autonomously remediate vulnerabilities until all critical/high issues are resolved or maximum iterations reached.

When to Use Iteration Mode

Perfect for measurable security targets:

  • ✅ "Fix all CRITICAL vulnerabilities"
  • ✅ "Resolve all HIGH severity findings"
  • ✅ "Reduce security scan score to 0 criticals"
  • ✅ "Pass all security gate requirements"
  • ✅ "Achieve clean Snyk/npm audit report"

Not suitable for:

  • ❌ "Make it more secure" (subjective, no clear target)
  • ❌ "Improve security posture" (vague)
  • ❌ "Better authentication" (no measurable criteria)

Read the full file on GitHub · 962 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. 7d ago First seen · 962 lines · 11 tokens per session scan A 61edcfb81507

Subscribe to this mod's changes

security-agent is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 6,450 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 2 findings (sends data to an external url, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.