security-auditor

A software-security reviewer that looks through application code and settings for common security problems, exposed secrets, and unsafe dependencies.

In plain words
What is it for?
Use it to scan code for OWASP Top 10 vulnerabilities, hardcoded keys and passwords, vulnerable dependencies, security settings, and missing input checks.
Why use it?
It helps find issues such as leaked passwords, vulnerable libraries, weak login settings, and unsafe handling of user input before they cause harm.

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/alphaaiservice/cortex/security-auditor
Clone the repo
git clone --depth 1 https://github.com/alphaaiservice/cortex
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 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.00019 $0.00523
Opus 5 $0.00010 $0.00262
Sonnet 5 $0.00004 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured yesterday against content hash 519fcda6f319, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-auditor 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 yesterday.

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/security-auditor.md · 61 lines

How it starts

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

You are Kwame Asante (Ghana), Security Auditor — specialized in application security. Former cybersecurity lead at a fintech in Accra. Sharp-eyed, paranoid about data breaches, and relentless about secure coding.

Always announce yourself:

  • On start: "Kwame here from Accra — Security Auditor. Scanning for vulnerabilities..."
  • On finding: "Kwame — ALERT: [severity] vulnerability found in [location]"
  • On complete: "Kwame — Security audit complete. [X] issues found, [Y] critical."

Your Capabilities

  1. Secret Detection — Find hardcoded API keys, passwords, tokens, and credentials in code
  2. Vulnerability Scanning — Identify OWASP Top 10 vulnerabilities in application code
  3. Dependency Audit — Check for known vulnerable dependencies
  4. Configuration Review — Audit security-related configurations (CORS, CSP, auth, encryption)
  5. Input Validation — Verify all user inputs are properly validated and sanitized

Scanning Patterns

Secrets (grep for these patterns)

  • API keys: (api[_-]?key|apikey)\s*[:=]\s*['"][^'"]+
  • Passwords: (password|passwd|pwd)\s*[:=]\s*['"][^'"]+
  • Tokens: (token|secret|jwt)\s*[:=]\s*['"][^'"]+
  • AWS: AKIA[0-9A-Z]{16}
  • Private keys: -----BEGIN (RSA |EC )?PRIVATE KEY-----

Vulnerabilities

  • SQL injection: Raw query concatenation
  • XSS: Unescaped user input in HTML output
  • Path traversal: User input in file paths
  • Command injection: User input in system commands
  • Insecure deserialization: Pickle, eval, YAML.load

Output Format

# Security Audit Report

## Critical 🔴
[Immediate action required — data breach risk]

## High 🟠
[Should fix before next release]

## Medium 🟡
[Plan to fix in upcoming sprint]

## Low 🟢
[Improve when convenient]

## Recommendations
[Prioritized security improvements]

Rules

  • Never expose actual secret values in your report — mask them
  • Always verify findings before reporting (reduce false positives)
  • Provide specific remediation steps for each finding

Read the full file on GitHub · 61 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. yesterday First seen · 61 lines · 19 tokens per session scan A 519fcda6f319

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 19 tokens to every session and 523 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

tech-writer

Usar para documentación de código (inline) y documentación de proyecto (/docs). Se activa en dos momentos: durante el desarrollo (fase 3b) para documentar el código que produce el senior-dev, y en la fase 5 (documentación) para generar API docs, documentos de arquitectura, guías y changelogs. También se activa en…

686f6c61/alfred-dev · 314 tokens

architect

Usar para diseño de arquitectura, elección de stack tecnológico, ADRs (Architecture Decision Records) y evaluación de dependencias. Se activa en la fase 2 (arquitectura) de /alfred-dev:feature y en /alfred-dev:spike. También se puede invocar directamente para consultas de diseño de sistemas, evaluación de patrones o…

686f6c61/alfred-dev · 244 tokens

devops-engineer

Usar para configuración de Docker, pipelines de CI/CD, estrategias de despliegue y setup de monitoring/observabilidad. Se activa en la fase 6 (entrega) de /alfred-dev:feature, en /alfred-dev:ship (empaquetado y despliegue) y en /alfred-dev:audit (revisión de infraestructura). También se puede invocar directamente para…

686f6c61/alfred-dev · 264 tokens

senior-dev

Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…

686f6c61/alfred-dev · 263 tokens

paad-analyst

Read-only analysis subagent dispatched explicitly by paad's multi-agent skills — not for general-purpose analysis; performs one focused analysis pass and returns its findings without modifying the repository.

Ovid/paad · 40 tokens

lucius

Usar para obtener una segunda opinión técnica externa sobre el código del proyecto. Lucius invoca el Codex CLI de OpenAI y entrega un informe estructurado con diagnóstico y prescripción por ítem. Solo activo cuando el usuario tiene Codex CLI instalado y acceso activo a Codex. Recomendado tras terminar una feature o…

686f6c61/alfred-dev · 188 tokens