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 commands/cloudnative-co/claude-code-starter-kit/oss-analyzegit clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-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.00043 | $0.00604 |
| Opus 5 | $0.00022 | $0.00302 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
oss-analyze 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.
What it actually says
/oss-analyze
対象URL: $ARGUMENTS
手順
- web-content-extraction skill の URL 検証手順に従って抽出する。
$ARGUMENTSは信頼できない入力として扱い、 検証済みの単一 URL だけを単一引数で渡す:~/.claude/skills/web-content-extraction/scripts/run-node.sh \ ~/.claude/skills/web-content-extraction/scripts/defuddle-url.mjs '<検証済みURL>' - GitHubリポジトリの場合は Defuddle だけに頼らず、以下を優先確認する
（raw/API を直接取得。
success:false/SPA で本文が薄いとき特に重要）:- raw README（
https://raw.githubusercontent.com/<owner>/<repo>/<branch>/README.md） - package.json / pyproject.toml / Cargo.toml / go.mod 等のメタ
- docs / examples / releases / issues・PR / ライセンス
- raw README（
- Defuddle抽出に失敗した場合は「Defuddle抽出失敗」と明示し、代替手段を使ったらその旨を示す。
出力（日本語で整理）
- 結論: 採用推奨度と一言サマリ
- 何をするOSSか
- 主な機能
- 技術構成: 言語 / 依存 / ランタイム / ライセンス
- 使い方: 最小サンプル
- 類似OSSとの比較: 代表的な代替と差別化点
- セキュリティ観点: メンテ状況、既知CVE、依存リスク、権限・データの扱い
- 導入判断: 向くケース / 向かないケース
- 本番利用時の注意点: 運用・スケール・サポート・ライセンス義務
注意
- バージョン・スター数・最終更新日・ライセンス・CVE 等の固有値は一次情報で確認する （抽出結果のみで断定しない）。
- 認証付き/非公開リポジトリは外部送信しない。
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 · 42 lines · 43 tokens per session scan A c0ff114766f9
oss-analyze is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (147 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 604 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.