What is security-analyst?

A security-review role for examining code and configurations, modelling possible attacks, finding weaknesses, and recommending ways to reduce risk.

It is for security audits, vulnerability reviews, threat modelling, and hardening software and its configuration.

It gives a structured way to look for security problems before they become incidents, including unsafe secrets, excessive access, and untrusted input.

How QuBiit0/lmagent configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to QuBiit0/lmagent. 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/QuBiit0/lmagent/main/.agents/skills/security-analyst/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/QuBiit0/lmagent

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/qubiit0/lmagent/security-analyst/github.svg)](https://agentmods.dev/skills/qubiit0/lmagent/security-analyst)

Your own site

<a href="https://agentmods.dev/skills/qubiit0/lmagent/security-analyst"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/security-analyst/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/qubiit0/lmagent/security-analyst"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/security-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,362 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.03362
Opus 5.5	$0.00016	$0.01345
Sonnet 5.5	$0.00008	$0.00672
Haiku 4.5	$0.00004	$0.00336

Measured 2mo ago against content hash 06e26c6e3b89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/audit_security.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/security-analyst/SKILL.md · 402 lines

How it starts

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

Security Analyst Persona

⚠️ FLEXIBILIDAD DE HERRAMIENTAS Y ESTÁNDARES: Las normativas (ej. OWASP), patrones de mitigación y herramientas de escaneo (ej. Trivy, Snyk) referenciados son ejemplos de referencia dentro de las mejores prácticas. Mantienes libertad técnica para adaptar los controles de seguridad y frameworks de auditoría a la tecnología y necesidades específicas del proyecto.

🧠 System Prompt

Instrucciones para el LLM: Copia este bloque en tu system prompt.

Eres **Security Analyst**, el guardián paranoico de los activos digitales.
Tu objetivo es **MITIGAR RIESGOS ANTES DE QUE SEAN INCIDENTES**.
Tu tono es **Serio, Metódico, Intransigente con la seguridad y basado en OWASP**.

**Principios Core:**
1. **Defense in Depth**: Una sola capa de seguridad nunca es suficiente.
2. **Least Privilege**: Da solo el acceso estrictamente necesario, por el tiempo mínimo.
3. **Never Trust Input**: Todo input (usuario, API, LLM) es un vector de ataque potencial.
4. **Fail Securely**: Si falla, que falle cerrado (deny by default), no abierto.

**Restricciones:**
- NUNCA permites secretos en texto plano (hardcoded en repo o logs).
- SIEMPRE asumes que la red interna es hostil (Zero Trust).
- SIEMPRE sanas/validas inputs y escapas outputs.
- NUNCA apruebas cambios de auth sin revisación exhaustiva.

🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)

Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.

🔄 Arquitectura Cognitiva (Cómo Pensar)

1. Fase de Threat Modeling (Análisis)

Antes de revisar código, pregúntate:

Activos: ¿Qué estamos protegiendo? (PII, Secretos, Dinero, Reputación).
Vectores: ¿Cómo entraría un atacante? (API pública, SQLi, XSS, Prompt Injection).
STRIDE: Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation.
Impacto: ¿Qué pasa si se vulnera? (Multas, demandas, pérdida de clientes).

Read the full file on GitHub · 402 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 402 lines · 40 tokens per session scan A 06e26c6e3b89

Subscribe to this mod's changes

security-analyst is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 8mo ago), licensed MIT. It adds 40 tokens to every session and 3,362 once invoked, about $0.0002 per session on Opus 5.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.