agentmods.dev

ipa-security-check

A static security checker that examines source code and configuration files for possible web vulnerabilities. Static checking means reviewing code without running the application; IPA is Japan’s Information-technology Promotion Agency.

In plain words
What is it for?
Use it to check for issues such as SQL injection, cross-site scripting, session problems, CSRF, unsafe headers, and access-control flaws, with optional path, category, severity, diff, and report filters.
Why use it?
It brings several IPA security checklists into one scan and attaches the relevant source reference to each result.

Skill for Claude CodeCodex

974 26d ago A scan 122 tokens original MIT
View the source file classmethod/tsumiki
Install

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.

agentmods
npx agentmods add skills/classmethod/tsumiki/ipa-security-check
Any agent
npx skills add classmethod/tsumiki --skill ipa-security-check
Clone the repo
git clone --depth 1 https://github.com/classmethod/tsumiki

Made for: Claude Code, Codex.

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,402 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00122 $0.03402
Opus 5 $0.00061 $0.01701
Sonnet 5 $0.00024 $0.00680
Haiku 4.5 $0.00012 $0.00340

Measured 2d ago against content hash 0195b95ec3f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ipa-security-check 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/render_report.py, scripts/snippet_hash.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/ipa-security-check/SKILL.md · 200 lines

How it starts

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

IPA Security Check Skill

このスキルが行うこと

IPA (情報処理推進機構) が公開する以下 5 資料の指摘事項に基づき、ローカルリポジトリのソースコード・設定ファイルを静的検査し、脆弱性候補を検出する。

略称 正式名称 主な検査内容
SWS 安全なウェブサイトの作り方 改訂第7版 11脆弱性 (SQLi/OSコマンド/トラバーサル/セッション/XSS/CSRF/HTTPヘッダ/メールヘッダ/クリックジャッキング/BoF/アクセス制御)
SQL 安全なSQLの呼び出し方 プレースホルダ使い分け・LIKE述語・識別子検証・文字コード問題
WHC ウェブ健康診断仕様 13診断項目のうち静的解析でカバー可能な観点
OPS 安全なウェブサイトの運用管理に向けての20ヶ条 HTTPヘッダ・依存ライブラリ・設定ファイル類
CL セキュリティ実装チェックリスト 改訂第7版 p.105-108 のチェックリスト

すべての検出結果に IPA 原典の document / section / page / url を必ず添えて返す。

起動方法

スラッシュコマンド /ipa-security-check で起動する。引数で対象スコープを指定する。

形式 動作
/ipa-security-check カレント WD 全体をスキャン
/ipa-security-check <path> 指定パス/glob のみ (例: src/, **/*.php)
/ipa-security-check --diff 現ブランチと main の差分ファイルのみ
/ipa-security-check --categories sqli,xss <path> カテゴリ限定
/ipa-security-check --severity high High 以上のみ
/ipa-security-check --output report.md,report.sarif 出力ファイル指定

自然文 (「IPA のセキュリティチェックをして」など) でも起動する。

実行手順 (Claude が行うこと)

  1. lib/scope_resolver.md を読み、引数を解釈して対象ファイル一覧と言語マッピングを作る
  2. lib/shard_planner.md を読み、カテゴリごとにファイル数を数え、閾値超過時は N 分割する
  3. agents/ 配下 の検査系サブエージェント (14 体) を メインから並列起動 する (公式制約によりサブエージェントから二次サブエージェントは起動できないため、分割はメイン側で行う)
  4. 各サブエージェントは findings[] を含む JSON を返す。メインは findings のみ集約してコード本文は文脈に保持せず、.tmp/ipa-security-check/findings_raw.json に書き出す
  5. Phase 5 (偽陽性レビュー):
    • scripts/snippet_hash.py を Bash で実行して findings_with_hash.json を作る
    • 15-false-positive-review エージェントを 5 件 / shard で並列起動し、返ってきた verdicts[] を結合して verdicts.json に保存
  6. Phase 6 + 出力 (Step 7): scripts/render_report.py を Bash で実行する。スクリプトが内部で以下を行う:
    • verdict を snippet_hash で findings にマージ
    • 既存 Markdown レポートから triage ブロックを抽出 (lib/triage_state.md 準拠) し、snippet_hash 一致で新 findings にステータス引き継ぎ
    • templates/report.md.tmpl を埋めて Markdown を出力、SARIF 2.1.0 も同時生成
  7. デフォルトの保存先は ./security-reports/ipa-security-report-YYYY-MM-DD-NN.md と ./security-reports/ipa-security-report-YYYY-MM-DD-NN.sarif (--output で上書き可)。security-reports/ ディレクトリが存在しない場合は自動作成する。同日に複数回実行した場合は連番 (-01, -02, ...) が自動付与され、既存レポートを上書きしない

Read the full file on GitHub · 200 lines

Files

What ships with it

54 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. 2d ago First seen · 200 lines · 122 tokens per session scan A 0195b95ec3f3

Subscribe to this mod's changes

ipa-security-check is a skill published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 26d ago), licensed MIT. It adds 122 tokens to every session and 3,402 once invoked, about $0.0006 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.

Security
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens