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 skills add Lord1Egypt/awesome-skill-forge --skill a2a-code-auditgit clone --depth 1 https://github.com/Lord1Egypt/awesome-skill-forgeWrote 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/lord1egypt/awesome-skill-forge/a2a-code-audit)<a href="https://agentmods.dev/skills/lord1egypt/awesome-skill-forge/a2a-code-audit"><img src="https://agentmods.dev/badge/skills/lord1egypt/awesome-skill-forge/a2a-code-audit.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.1 | $0.00000 | $0.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
a2a-code-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 7d 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.
What it actually says
Code Audit & Security Scan
Static code analysis for security vulnerabilities, style violations, and bugs.
When to Use
Trigger on: "audit code", "scan for bugs", "security check", "code review", "find vulnerabilities"
What This Does
- Analyzes code for common security issues
- Checks for style violations
- Identifies potential bugs
- Returns structured report with severity levels
Supported Languages
- Python
- JavaScript/TypeScript
Workflow
Step 1: Receive Code
Get code to analyze + language.
Step 2: Static Analysis
Analyze using pattern matching and heuristics:
Python checks:
- Use of eval(), exec(), import()
- Hardcoded credentials
- SQL injection risks
- Path traversal
- Insecure random
JS/TS checks:
- eval() usage
- innerHTML without sanitization
- Hardcoded API keys
- console.log in production code
Step 3: Scoring
Score = 100 - (issues_found × severity_weight)
Verdict: PASS (>80), WARN (50-80), FAIL (<50)
Step 4: Present Results
## Code Audit: [language]
### Summary
| Metric | Value |
|--------|-------|
| Score | [X]/100 |
| Verdict | [PASS/WARN/FAIL] |
| Issues | [N] |
### Issues
1. [SEVERITY] [issue description] (line [N])
2. ...
### Recommendations
- [fix suggestions]
No External Tools Required
This skill uses only:
- Platform exec tool
- Pattern matching
- No external binaries needed
Example
## Code Audit: Python
### Summary
| Metric | Value |
|--------|-------|
| Score | 70/100 |
| Verdict | WARN |
| Issues | 3 |
### Issues
1. HIGH: eval() usage (line 2)
2. MEDIUM: hardcoded 'password' (line 5)
3. LOW: unused import 'os' (line 1)
### Recommendations
- Replace eval() with safer alternatives
- Use environment variables for secrets
- Remove unused imports
Notes
- Works with platform tools only
- No install steps required
- Pattern-based analysis (not full compiler)
- Always note limitations in report
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.
- 7d ago First seen · 104 lines · 0 tokens per session scan A a358c27e483a
a2a-code-audit is a skill published in the GitHub repository Lord1Egypt/awesome-skill-forge (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…