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 skills/bugrabilge/bilge-development-kit/securitynpx skills add bugrabilge/bilge-development-kit --skill securitygit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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.00048 | $0.00781 |
| Opus 5 | $0.00024 | $0.00391 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
security 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security - Security Audit
$ARGUMENTS
Purpose
This command performs a comprehensive security audit on the project using security-auditor and penetration-tester agents.
Sub-commands
/security - Full security audit
/security quick - Quick scan (secrets + dependencies only)
/security auth - Authentication/authorization review
/security deps - Dependency vulnerability scan
/security owasp - OWASP Top 10 checklist review
Behavior
When /security is triggered:
-
Automated scans
# Run security scan script python .agent/skills/vulnerability-scanner/scripts/security_scan.py . # Run dependency analysis python .agent/skills/vulnerability-scanner/scripts/dependency_analyzer.py . # Check for secrets in code # (included in security_scan.py) -
Agent analysis
- Invoke
security-auditoragent for code review - Invoke
penetration-testeragent for attack surface analysis
- Invoke
-
OWASP Top 10:2025 checklist
# Category Check A01 Broken Access Control IDOR, auth bypass, SSRF A02 Security Misconfiguration Headers, CORS, defaults A03 Supply Chain Dependencies, lock files A04 Cryptographic Failures Weak crypto, exposed secrets A05 Injection SQL, XSS, command injection A06 Insecure Design Architecture flaws A07 Auth Failures Session, MFA, credentials A08 Integrity Failures Unsigned updates A09 Logging Failures Missing audit trails A10 Exceptional Conditions Error handling, fail-open -
Generate report
Output Format
## Security Audit Report
### Scan Results
- Security Scan: PASS/FAIL
- Dependency Audit: X vulnerabilities (Y critical)
- Secrets Check: PASS/FAIL
### Findings by OWASP Category
#### A01: Broken Access Control
- [Finding or "No issues found"]
#### A05: Injection
- [Finding or "No issues found"]
[... all categories ...]
### Risk Summary
| Severity | Count | Action |
|----------|-------|--------|
| Critical | X | Fix immediately |
| High | X | Fix before deploy |
| Medium | X | Schedule fix |
| Low | X | Document |
### Recommendations
1. [Priority fix with details]
2. [Secondary fix]
### Next Steps
- [ ] Fix critical findings
- [ ] Re-run `/security quick` to verify
- [ ] Schedule medium/low fixes
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.
- 2d ago First seen · 134 lines · 48 tokens per session scan A a86e82f811fe
security is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 781 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…