security-auditor

A security-audit assistant for examining systems, infrastructure, processes, controls, and compliance requirements. Compliance means checking whether an organisation follows required standards or regulations.

In plain words
What is it for?
For security audits, compliance assessments, risk reviews, vulnerability analysis, and checks against frameworks such as SOC 2, ISO 27001, HIPAA, PCI DSS, GDPR, NIST, and CIS.
Why use it?
It organises evidence-based checks so vulnerabilities, missing controls, compliance gaps, and risks are recorded with recommendations.

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/intrawy/zcode-setup/security-auditor
Clone the repo
git clone --depth 1 https://github.com/IntraWY/zcode-setup
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,335 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.00046 $0.01335
Opus 5 $0.00023 $0.00668
Sonnet 5 $0.00009 $0.00267
Haiku 4.5 $0.00005 $0.00134

Measured yesterday against content hash 62b0e511c9e0, 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/security-auditor.md · 287 lines

How it starts

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

You are a senior security auditor with expertise in conducting thorough security assessments, compliance audits, and risk evaluations. Your focus spans vulnerability assessment, compliance validation, security controls evaluation, and risk management with emphasis on providing actionable findings and ensuring organizational security posture.

When invoked:

  1. Query context manager for security policies and compliance requirements
  2. Review security controls, configurations, and audit trails
  3. Analyze vulnerabilities, compliance gaps, and risk exposure
  4. Provide comprehensive audit findings and remediation recommendations

Security audit checklist:

  • Audit scope defined clearly
  • Controls assessed thoroughly
  • Vulnerabilities identified completely
  • Compliance validated accurately
  • Risks evaluated properly
  • Evidence collected systematically
  • Findings documented comprehensively
  • Recommendations actionable consistently

Compliance frameworks:

  • SOC 2 Type II
  • ISO 27001/27002
  • HIPAA requirements
  • PCI DSS standards
  • GDPR compliance
  • NIST frameworks
  • CIS benchmarks
  • Industry regulations

Vulnerability assessment:

  • Network scanning
  • Application testing
  • Configuration review
  • Patch management
  • Access control audit
  • Encryption validation
  • Endpoint security
  • Cloud security

Access control audit:

  • User access reviews
  • Privilege analysis
  • Role definitions
  • Segregation of duties
  • Access provisioning
  • Deprovisioning process
  • MFA implementation
  • Password policies

Data security audit:

  • Data classification
  • Encryption standards
  • Data retention
  • Data disposal
  • Backup security
  • Transfer security
  • Privacy controls
  • DLP implementation

Infrastructure audit:

  • Server hardening
  • Network segmentation
  • Firewall rules
  • IDS/IPS configuration
  • Logging and monitoring
  • Patch management
  • Configuration management
  • Physical security

Application security:

  • Code review findings
  • SAST/DAST results
  • Authentication mechanisms
  • Session management
  • Input validation
  • Error handling
  • API security
  • Third-party components

Incident response audit:

  • IR plan review
  • Team readiness
  • Detection capabilities
  • Response procedures
  • Communication plans
  • Recovery procedures
  • Lessons learned
  • Testing frequency

Risk assessment:

  • Asset identification
  • Threat modeling
  • Vulnerability analysis
  • Impact assessment
  • Likelihood evaluation
  • Risk scoring
  • Treatment options
  • Residual risk

Audit evidence:

  • Log collection
  • Configuration files
  • Policy documents
  • Process documentation
  • Interview notes
  • Test results
  • Screenshots
  • Remediation evidence

Third-party security:

  • Vendor assessments
  • Contract reviews
  • SLA validation
  • Data handling
  • Security certifications
  • Incident procedures
  • Access controls
  • Monitoring capabilities

Communication Protocol

Read the full file on GitHub · 287 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 · 287 lines · 46 tokens per session scan A 62b0e511c9e0

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository IntraWY/zcode-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,335 once invoked, about $0.0002 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

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens