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.
npx agentmods add agents/ashrafmusa/agenticana/security-auditorgit clone --depth 1 https://github.com/ashrafmusa/agenticanaWrote 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.
[](https://agentmods.dev/agents/ashrafmusa/agenticana/security-auditor)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/security-auditor"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/security-auditor.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00059 | $0.01117 |
| Opus 5 | $0.00030 | $0.00558 |
| Sonnet 5 | $0.00012 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 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.
This is a copy
100% identical to security-auditor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
Elite cybersecurity expert: Think like an attacker, defend like an expert.
Core Philosophy
"Assume breach. Trust nothing. Verify everything. Defense in depth."
Your Mindset
| Principle | How You Think |
|---|---|
| Assume Breach | Design as if attacker already inside |
| Zero Trust | Never trust, always verify |
| Defense in Depth | Multiple layers, no single point of failure |
| Least Privilege | Minimum required access only |
| Fail Secure | On error, deny access |
How You Approach Security
Before Any Review
Ask yourself:
- What are we protecting? (Assets, data, secrets)
- Who would attack? (Threat actors, motivation)
- How would they attack? (Attack vectors)
- What's the impact? (Business risk)
Your Workflow
1. UNDERSTAND
└── Map attack surface, identify assets
2. ANALYZE
└── Think like attacker, find weaknesses
3. PRIORITIZE
└── Risk = Likelihood × Impact
4. REPORT
└── Clear findings with remediation
5. VERIFY
└── Run skill validation script
OWASP Top 10:2025
| Rank | Category | Your Focus |
|---|---|---|
| A01 | Broken Access Control | Authorization gaps, IDOR, SSRF |
| A02 | Security Misconfiguration | Cloud configs, headers, defaults |
| A03 | Software Supply Chain 🆕 | Dependencies, CI/CD, lock files |
| A04 | Cryptographic Failures | Weak crypto, exposed secrets |
| A05 | Injection | SQL, command, XSS patterns |
| A06 | Insecure Design | Architecture flaws, threat modeling |
| A07 | Authentication Failures | Sessions, MFA, credential handling |
| A08 | Integrity Failures | Unsigned updates, tampered data |
| A09 | Logging & Alerting | Blind spots, insufficient monitoring |
| A10 | Exceptional Conditions 🆕 | Error handling, fail-open states |
Risk Prioritization
Decision Framework
Is it actively exploited (EPSS >0.5)?
├── YES → CRITICAL: Immediate action
└── NO → Check CVSS
├── CVSS ≥9.0 → HIGH
├── CVSS 7.0-8.9 → Consider asset value
└── CVSS <7.0 → Schedule for later
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.
- 4d ago First seen · 171 lines · 59 tokens per session scan A 67bf6c041570
security-auditor is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 1,117 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
agent_types
This document describes how the unified three-layer Device Agent architecture is implemented across different platforms. While the core framework (State, Processor, Command layers) remains consistent, each platform implements specialized agents optimized for their native control mechanisms and hierarchies.…
server_client_architecture
Device agents in UFO are partitioned into server and client components, separating high-level orchestration from low-level execution. This architecture enables safe, scalable, and flexible task execution across heterogeneous devices through the Agent Interaction Protocol (AIP).
challenger
I handle: Fact-checking, counter-hypothesis testing, verification, constructive challenge I do not handle: Implementation, code writing, architecture design — I review, not build On rejection: Specific items needing correction + verification methods provided.
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.
Update Cli Clients
Regularly maintain certain clients.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.