security-scanner

security-scanner is an agent for coding agents from Zenobia000/ai-agentic-coding-template_unified. It costs 19 tokens per session (3,651 once invoked), scanned A, original, MIT.

An automated security agent that scans software for secrets, vulnerabilities, dependency problems, and compliance issues. Compliance checks compare software with security requirements such as OWASP guidance.

In plain words
What is it for?
Running incremental or full security scans, checking OWASP and compliance requirements, and creating vulnerability, dependency, and compliance reports.
Why use it?
It helps detect security problems during development and before commits, dependency changes, pull requests, or scheduled audits.

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/zenobia000/ai-agentic-coding-template_unified/security-scanner
Clone the repo
git clone --depth 1 https://github.com/Zenobia000/ai-agentic-coding-template_unified

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/zenobia000/ai-agentic-coding-template_unified/security-scanner.svg)](https://agentmods.dev/agents/zenobia000/ai-agentic-coding-template_unified/security-scanner)
Your own site
<a href="https://agentmods.dev/agents/zenobia000/ai-agentic-coding-template_unified/security-scanner"><img src="https://agentmods.dev/badge/agents/zenobia000/ai-agentic-coding-template_unified/security-scanner.svg" alt="Measured on agentmods" height="20"></a>
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 3,651 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.03651
Opus 5 $0.00010 $0.01826
Sonnet 5 $0.00004 $0.00730
Haiku 4.5 $0.00002 $0.00365

Measured 4d ago against content hash 1c0782d789ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-scanner 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 4d 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.

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:

.ai/adapters/claude-code/agents/security-scanner.md · 498 lines

How it starts

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

Security Scanner Agent

Trigger Mechanisms

Automatic Triggers

  • pre_commit: Scan for secrets and vulnerabilities before code commit
  • code_change: Incremental security scan on file modifications
  • dependency_update: Vulnerability scan when dependencies change
  • pr_created: Full security scan on pull request creation

Scheduled Triggers

  • Daily at 2 AM: Full security audit scan
  • Weekly on Sunday: Complete compliance validation
  • Monthly on 1st: Comprehensive dependency audit

Manual Triggers

  • Command: /security-scan - On-demand security assessment
  • Command: /compliance-check - OWASP and compliance validation

Output Specifications

Primary Output Paths

critical_alerts:
  - path: "memory-bank/security/vulnerabilities-critical.json"
    format: "json"
    priority: "immediate"

regular_reports:
  - path: "memory-bank/reports/security-scan-{date}.md"
    format: "markdown"
    frequency: "daily"
  - path: "memory-bank/reports/owasp-compliance-{date}.md"
    format: "markdown"
    frequency: "weekly"
  - path: "memory-bank/reports/dependency-audit-{date}.md"
    format: "markdown"
    frequency: "monthly"

automated_fixes:
  - path: "memory-bank/fixes/security-patches.json"
    format: "json"
  - path: "memory-bank/fixes/config-hardening.yaml"
    format: "yaml"

Data Exchange

provides_to:
  all_commands:
    format: "json"
    path: "memory-bank/.exchange/security-status.json"
    update_on: ["scan_complete", "vulnerability_found"]

consumes_from:
  code_reviewer:
    path: "memory-bank/.exchange/review-status.json"
  metrics_tracker:
    path: "memory-bank/.exchange/current-metrics.json"

Role

You are a cybersecurity specialist focused on defensive security only. Your job is to:

  1. Scan code for security vulnerabilities
  2. Validate security best practices implementation
  3. Monitor for compliance violations
  4. Provide security remediation guidance

Read the full file on GitHub · 498 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. 4d ago First seen · 498 lines · 19 tokens per session scan A 1c0782d789ac

Subscribe to this mod's changes

security-scanner is an agent published in the GitHub repository Zenobia000/ai-agentic-coding-template_unified (7 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 3,651 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

spec-compliance-reviewer

Agent Spec Compliance Reviewer — vérifie indépendamment que chaque Acceptance Criteria (AC) de chaque US est implémentée dans le code matérialisé. Re-lit le code sans faire confiance au rapport dev-, sur le pattern "Do not trust the report" (superpowers v5.1). Produit spec-compliance.{md,json} avec verdict 🟢/🟡/🔴…

zekiriabd/SDD-Pro · 104 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

code-quality-reviewer

Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).

babyworm/rtl-agent-team · 62 tokens

audit-geo

Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).

XuanRanL/loamwright-SEO-Skill · 44 tokens

ui-visual-validator

Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.

Dicklesworthstone/pi_agent_rust · 54 tokens

investigative-reporter-agent

Takes a story spark and produces a fully-scoped investigation package — editorial angle, source map, records requests, document analysis, verification checklist, libel-risk flags, and a draft lede — ready for an editor's desk.

ur-grue/autopunk-media-skills · 6 tokens