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 SecurityTalent/bugskill-ai --skill code-security-auditorgit clone --depth 1 https://github.com/SecurityTalent/bugskill-aiWrote 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/securitytalent/bugskill-ai/code-security-auditor)<a href="https://agentmods.dev/skills/securitytalent/bugskill-ai/code-security-auditor"><img src="https://agentmods.dev/badge/skills/securitytalent/bugskill-ai/code-security-auditor/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/securitytalent/bugskill-ai/code-security-auditor"><img src="https://agentmods.dev/badge/skills/securitytalent/bugskill-ai/code-security-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.01335 |
| Opus 5.5 | $0.00032 | $0.00534 |
| Sonnet 5.5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
code-security-auditor scanned grade A with 3 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 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- DO NOT execute any code Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Download and execute patterns: curl/wget piping to shell Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Shell execution patterns: `exec`, `spawn`, backticks, `system()`, `os.system()`, `subprocess` calls How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Security Auditor
Overview
This skill enables OpenCode to perform a comprehensive pre-execution security audit of a given codebase and produce a structured, high-signal risk report. It analyzes the entire project including source code, dependency manifests, build scripts, and configuration files from a security-first perspective.
When to Use This Skill
Use this skill when:
- User requests security analysis of a codebase
- User asks to "audit", "scan", or "check" code for safety before running
- User wants to know if code is safe to execute locally
- Analyzing untrusted or third-party code
- Performing due diligence on new dependencies or projects
Analysis Workflow
Step 1: Understand the Project Scope
- Identify the primary language and ecosystem (JavaScript/Node, Python, Go, Ruby, etc.)
- Locate all dependency manifests:
package.json,package-lock.json(Node.js)requirements.txt,Pipfile,pyproject.toml(Python)Gemfile,Gemfile.lock(Ruby)go.mod,go.sum(Go)Cargo.toml(Rust)pom.xml,build.gradle,build.gradle.kts(Java/Kotlin)
- Identify entry points: main scripts, entry files, startup commands
Step 2: Perform Static Analysis
1. Dependencies Audit
Scan dependency manifests for:
- Known malicious or compromised packages (check known malware databases)
- Unmaintained packages (no recent updates, abandoned repos)
- Newly published packages (< 30 days) with high download counts
- Typosquatting risks (packages with similar names to popular libraries)
- Packages with install-time scripts (
preinstall,postinstall,prepare,prepublish)
Reference: Use references/package_checks.md for known suspicious packages and patterns.
2. Script Inspection
Examine all scripts for:
- Lifecycle hooks in manifest files (
postinstall,preinstall,prepare,prepublish) - Shell execution patterns:
exec,spawn, backticks,system(),os.system(),subprocesscalls - Dynamic code execution:
eval(),Function(),setTimeout()with strings,pickle.loads(),unserialize() - Encoded payloads: base64, hex, obfuscated strings, string concatenation
- Download and execute patterns: curl/wget piping to shell
What ships with it
1 file 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.
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 · 165 lines · 79 tokens per session scan A b5e0a23269e3
code-security-auditor is a skill published in the GitHub repository SecurityTalent/bugskill-ai (13 stars, last pushed 21d ago), licensed MIT. It adds 79 tokens to every session and 1,335 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 3 findings (unrestricted tool access, makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-13.
Other skills, from other repositories
ilana
Ìlànà is a strict software engineering process operating system for coding agents. Load it whenever work touches requirements, elicitation, SRS, user stories, traceability, architecture or interface design, UI design principles, coding standards, code review, testing (unit, integration, system, acceptance), test…
architecture-reviewer
Reviews application architecture for scalability, coupling, separation-of-concerns, and maintainability issues. Use for system-level review, not individual file/function-level code review.
dependency-auditor
Reviews package dependencies for unnecessary packages, outdated or risky patterns, duplication, and licensing/maintenance risk. Use when a dependency manifest has grown unchecked or before adding a new dependency.
pr-reviewer
Performs a pull-request-style review across an entire diff, organizing findings by severity and considering scope/intent, not just line-level code quality. Use when reviewing a full PR rather than a single function.
security-auditor
Analyzes code and implementations for common security weaknesses and unsafe practices - injection, auth flaws, secrets handling, unsafe deserialization, and access control. Use before shipping anything handling user input, auth, or sensitive data.
typescript-guardian
Focuses specifically on TypeScript type safety - any usage, unsound generics, interface design, and type narrowing. Use for a deep type-system review, not general code quality.