Borrowing it
Nothing to install: this file belongs to davidmatousek/tachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/skills/security/SKILL.mdgit clone --depth 1 https://github.com/davidmatousek/tachiWrote 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/skills/davidmatousek/tachi/security)<a href="https://agentmods.dev/skills/davidmatousek/tachi/security"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidmatousek/tachi/security"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00165 | $0.08338 |
| Opus 5.5 | $0.00066 | $0.03335 |
| Sonnet 5.5 | $0.00033 | $0.01668 |
| Haiku 4.5 | $0.00016 | $0.00834 |
Grade A, and why
security scanned grade A with 1 finding 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Command Injection: `os.system(var)`, `subprocess.call(f"cmd {var}")`, `exec(user_input)` Copies of this mod
1 near-identical copy found in the catalogue:
- security — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 818 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security — SAST/SCA Security Scan
Purpose: Analyze code files and dependency manifests changed on the feature branch for OWASP Top 10 vulnerabilities and known CVE patterns. Write permanent audit artifacts. Block on CRITICAL/HIGH findings until acknowledged or fixed.
When invoked from /aod.build: Called as the Security Scan step (Step 7) via the Skill tool. --no-security flag in /aod.build bypasses this skill entirely.
When invoked standalone: Run directly as /security from any project directory. security-scan.md is written to specs/{NNN}-*/ if inside an AOD project, or to the current working directory otherwise.
Step 0: Parse Arguments
If invoked standalone, parse optional flags from arguments:
-
--no-security: If present (standalone invocation context), output "Security scan skipped (--no-security)" and exit cleanly. This flag is normally handled by/aod.buildStep 0 before invoking this skill; if present here in standalone mode, honor it. -
Feature number extraction: Detect current feature number from branch name (
git branch --show-current→ extract leading digits) or fromspecs/*/directory listing. Used for output path resolution. -
Output path resolution:
- If inside an AOD project (
specs/{NNN}-*/exists): writesecurity-scan.mdtospecs/{NNN}-*/security-scan.md - Otherwise: write
security-scan.mdto current working directory
- If inside an AOD project (
Step 1: File Detection
Detect all files changed on the feature branch relative to main.
1a: SAST File Detection (FR-004)
Run: git diff --name-only main...HEAD
Filter the output to code files by including only these extensions:
.py .js .ts .jsx .tsx .sh .go .rs .java .rb .swift .kt .php .cs .cpp .c .h
Exclude these patterns from the result:
- Generated files:
*.lock,*.min.js,*.min.css,*.map,*.generated.* - Directories:
vendor/,dist/,build/,node_modules/,.aod/,docs/
Store result as code_files list. Count as code_file_count.
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.
- 1mo ago First seen · 818 lines · 165 tokens per session scan A c4e86f44ad04
security is a skill published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 4d ago), licensed Apache-2.0. It adds 165 tokens to every session and 8,338 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
usap-alex
Universal USAP security advisor (cs-security-analyst). Use for any security question, alert triage (AT), threat hunt (TH), compromise assessment (CA), or when the user says "activate Alex", "start USAP", or asks what USAP can do.
usap-ciso
CISO and executive security advisor (cs-ciso-advisor). Use for board reports, executive risk briefings, regulatory gap assessments, cyber insurance inputs, or when the user says "board report", "CISO brief", "executive summary", "risk posture for leadership", or "regulatory update".
usap-incident-responder
Active incident command and response (cs-incident-responder). Use when there is a confirmed or suspected active incident, for containment decisions, forensic investigation, SEV declaration, or when the user says "declare incident", "start IR", "we have an active breach", or "forensics".
usap-red-teamer
Offensive security coordinator (cs-red-teamer). Use for red team campaign planning, attack path analysis, engagement scoping, adversary simulation, or when the user says "red team", "pentest", "attack simulation", "run an engagement", or "offensive security". Requires explicit authorization scope.
pipeline-security-scan
../../../appsec-devsecops/pipeline-security-scan/SKILL.md.