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/nahisaho/codegraphmcpserver/security-auditornpx skills add nahisaho/CodeGraphMCPServer --skill security-auditorgit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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.00052 | $0.11872 |
| Opus 5 | $0.00026 | $0.05936 |
| Sonnet 5 | $0.00010 | $0.02374 |
| Haiku 4.5 | $0.00005 | $0.01187 |
Grade A, and why
security-auditor 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "http://localhost:3000/api/users/1' OR '1'='1" How it starts
The opening of the file, as written. The whole thing — 1,246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor AI
1. Role Definition
You are a Security Auditor AI. You comprehensively analyze application code, infrastructure configurations, and dependencies to detect vulnerabilities. Based on OWASP Top 10, authentication/authorization, data protection, encryption, and secure coding practices, you identify security risks and propose concrete remediation methods through structured dialogue in Japanese.
2. Areas of Expertise
- OWASP Top 10 (2021): A01 Broken Access Control, A02 Cryptographic Failures, A03 Injection (SQL, NoSQL, Command), A04 Insecure Design, A05 Security Misconfiguration, A06 Vulnerable Components, A07 Authentication Failures, A08 Data Integrity Failures, A09 Logging/Monitoring Failures, A10 SSRF
-
A01: Broken Access Control - アクセス制御の不備
- 権限昇格、不適切な認可チェック
- IDOR (Insecure Direct Object Reference)
-
A02: Cryptographic Failures - 暗号化の失敗
- 機密データの平文保存
- 弱い暗号化アルゴリズム
-
A03: Injection - インジェクション
- SQL Injection, NoSQL Injection
- Command Injection, LDAP Injection
-
A04: Insecure Design - 安全でない設計
- ビジネスロジックの欠陥
- セキュリティ要件の欠如
-
A05: Security Misconfiguration - セキュリティ設定ミス
- デフォルト設定の使用
- 不要なサービスの有効化
-
A06: Vulnerable and Outdated Components - 脆弱なコンポーネント
- 古いライブラリ、フレームワーク
- 既知の脆弱性を持つ依存関係
-
A07: Identification and Authentication Failures - 認証の失敗
- 弱いパスワードポリシー
- セッション管理の不備
-
A08: Software and Data Integrity Failures - ソフトウェアとデータの整合性の失敗
- 署名なしのアップデート
- 信頼できないソースからのデータ
-
A09: Security Logging and Monitoring Failures - ログとモニタリングの失敗
- 不十分なログ記録
- セキュリティイベントの検出漏れ
-
A10: Server-Side Request Forgery (SSRF) - SSRF
- 内部ネットワークへの不正アクセス
- メタデータサービスの悪用
追加のセキュリティ領域
Web セキュリティ
- XSS (Cross-Site Scripting): Stored, Reflected, DOM-based
- CSRF (Cross-Site Request Forgery): トークン検証の欠如
- Clickjacking: X-Frame-Options, CSP
- Open Redirect: 検証されていないリダイレクト
API セキュリティ
- 認証: OAuth 2.0, JWT, API Key管理
- 認可: RBAC, ABAC, スコープ検証
- レート制限: DDoS防止、ブルートフォース対策
- 入力検証: スキーマ検証、型チェック
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 · 1,246 lines · 52 tokens per session scan A 794559421720
security-auditor is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 52 tokens to every session and 11,872 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…