security

security is a command for coding agents from Fmarzochi/EGC. It costs 4 tokens per session (460 once invoked), scanned A, original, Apache-2.0.

Run comprehensive security review.

Command

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 commands/fmarzochi/egc/security
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/fmarzochi/egc/security.svg)](https://agentmods.dev/commands/fmarzochi/egc/security)
Your own site
<a href="https://agentmods.dev/commands/fmarzochi/egc/security"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/security.svg" alt="Measured on agentmods" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00004 $0.00460
Opus 5 $0.00002 $0.00230
Sonnet 5 $0.00001 $0.00092
Haiku 4.5 $0.00000 $0.00046

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

Security

Grade A, and why

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 today.

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.

.opencode/commands/security.md · 90 lines

What it actually says

Security Review Command

Conduct a comprehensive security review: $ARGUMENTS

Your Task

Analyze the specified code for security vulnerabilities following OWASP guidelines and security best practices.

Security Checklist

OWASP Top 10

  1. Injection (SQL, NoSQL, OS command, LDAP)

    • Check for parameterized queries
    • Verify input sanitization
    • Review dynamic query construction
  2. Broken Authentication

    • Password storage (bcrypt, argon2)
    • Session management
    • Multi-factor authentication
    • Password reset flows
  3. Sensitive Data Exposure

    • Encryption at rest and in transit
    • Proper key management
    • PII handling
  4. XML External Entities (XXE)

    • Disable DTD processing
    • Input validation for XML
  5. Broken Access Control

    • Authorization checks on every endpoint
    • Role-based access control
    • Resource ownership validation
  6. Security Misconfiguration

    • Default credentials removed
    • Error handling doesn't leak info
    • Security headers configured
  7. Cross-Site Scripting (XSS)

    • Output encoding
    • Content Security Policy
    • Input sanitization
  8. Insecure Deserialization

    • Validate serialized data
    • Implement integrity checks
  9. Using Components with Known Vulnerabilities

    • Run npm audit
    • Check for outdated dependencies
  10. Insufficient Logging & Monitoring

    • Security events logged
    • No sensitive data in logs
    • Alerting configured

Additional Checks

  • Secrets in code (API keys, passwords)
  • Environment variable handling
  • CORS configuration
  • Rate limiting
  • CSRF protection
  • Secure cookie flags

Report Format

Critical Issues

[Issues that must be fixed immediately]

High Priority

[Issues that should be fixed before release]

Recommendations

[Security improvements to consider]


IMPORTANT: Security issues are blockers. Do not proceed until critical issues are resolved.

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. today First seen · 90 lines · 4 tokens per session scan A 9e8bc8c6f30c

Subscribe to this mod's changes

security is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 4 tokens to every session and 460 once invoked, about $0.0000 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-09-03.