auto-co-meta: Skill for Claude Code

.claude/skills/security-audit/SKILL.md

security-audit is a skill for Claude Code from NikitaDmitrieff/auto-co-meta. It costs 49 tokens per session (586 once invoked), scanned A, original, MIT.

A guide for systematically reviewing application code, dependencies, and configuration for common security weaknesses.

In plain words
What is it for?
Use it for code, dependency, configuration, architecture, or API security reviews, especially before deployment or after changes to public endpoints.
Why use it?
It helps find issues such as injection, cross-site scripting, authentication mistakes, exposed secrets, unsafe permissions, and vulnerable package versions before they cause harm.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is NikitaDmitrieff/auto-co-meta's own configuration. It tells Claude Code how to work on auto-co-meta itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything auto-co-meta configures →

Reuse

Borrowing it

Nothing to install: this file belongs to NikitaDmitrieff/auto-co-meta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NikitaDmitrieff/auto-co-meta/main/.claude/skills/security-audit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/NikitaDmitrieff/auto-co-meta

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/nikitadmitrieff/auto-co-meta/security-audit.svg)](https://agentmods.dev/skills/nikitadmitrieff/auto-co-meta/security-audit)
Your own site
<a href="https://agentmods.dev/skills/nikitadmitrieff/auto-co-meta/security-audit"><img src="https://agentmods.dev/badge/skills/nikitadmitrieff/auto-co-meta/security-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00049 $0.00586
Opus 5 $0.00024 $0.00293
Sonnet 5 $0.00010 $0.00117
Haiku 4.5 $0.00005 $0.00059

Measured 8d ago against content hash 49593d464763, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

security-audit 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 8d 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.

.claude/skills/security-audit/SKILL.md · 54 lines

How it starts

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

Security Audit

Systematic security review for application code, dependencies, and configuration.

Not a replacement for professional penetration testing. Identifies common vulnerabilities within scope of code review.

Audit Types

Type Focus When to Use
Code Review OWASP Top 10, injection, auth New features, PRs, suspicious code
Dependency CVEs, outdated packages Before deploy, periodic, CI/CD
Configuration Secrets, permissions, hardening Infrastructure changes, new envs
Architecture Attack surface, data flow Design phase, major refactors
API Security Auth, authz, rate limiting New endpoints, public APIs

When NOT to Use

  • Designing new auth flows — Use api-design for designing OAuth2/JWT endpoints from scratch
  • Performance issues — Use performance-optimization even if caused by auth overhead
  • CI/CD pipeline security — Use ci-cd for pipeline hardening (secret management, permissions)

Key Principles

  • Scope first — Define audit area, depth, and constraints before scanning
  • Classify severity — Critical (24-48h), High (1 week), Medium (2-4 weeks), Low (backlog)
  • Remediate or track — Fix critical issues immediately, create ohno tasks for the rest
  • No secrets in code — Scan for hardcoded credentials, API keys, connection strings

Quick Start Checklist

  1. Define audit scope and type (code, dependency, config, architecture, API)
  2. Run automated scans (npm audit, grep patterns, secret detection)
  3. Review findings and classify severity using decision tree in references
  4. Remediate critical/high findings immediately
  5. Create ohno tasks for medium/low findings with appropriate priority
  6. Document findings in audit report

References

Reference Description
owasp-top-10.md OWASP vulnerabilities with detection and fixes
dependency-security.md npm audit, pip-audit, Snyk, CI/CD integration
auth-patterns.md Secure authentication and authorization patterns
api-security.md API-specific security concerns
secrets-management.md Handling sensitive configuration

Read the full file on GitHub · 54 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 54 lines · 49 tokens per session scan A 49593d464763

Subscribe to this mod's changes

security-audit is a skill published in the GitHub repository NikitaDmitrieff/auto-co-meta (43 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 586 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-30.