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/crearize/ai-dev-helm/generate-docsnpx skills add Crearize/ai-dev-helm --skill generate-docsgit clone --depth 1 https://github.com/Crearize/ai-dev-helmWhat 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.00030 | $0.01169 |
| Opus 5 | $0.00015 | $0.00584 |
| Sonnet 5 | $0.00006 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
generate-docs 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Generation - ドキュメント自動生成
git logから CHANGELOG とリリースノートを自動生成する。リリース時に手動呼び出しして使用する。
実行フロー
Step 1: バージョン情報の確認
↓
Step 2: git log の解析
↓
Step 3: CHANGELOG.md の更新
↓
Step 4: リリースノート生成
↓
Step 5: ユーザー確認
Step 1: バージョン情報の確認
前回リリースタグの取得
# タグ命名規則: vX.Y.Z
git describe --tags --abbrev=0
タグがない場合（初回リリース）は全コミットを対象とする。
次のバージョンの決定
ユーザーに確認する。デフォルト提案としてコミットタイプから推定：
| コミット内容 | バージョンアップ | 例 |
|---|---|---|
feat: が含まれる |
マイナー | v1.0.0 -> v1.1.0 |
fix: のみ |
パッチ | v1.0.0 -> v1.0.1 |
breaking change（! suffix） |
メジャー | v1.0.0 -> v2.0.0 |
Step 2: git log の解析
# 前回タグからのコミット取得
PREV_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$PREV_TAG" ]; then
git log --oneline --no-merges
else
git log ${PREV_TAG}..HEAD --oneline --no-merges
fi
コミットメッセージの type でカテゴリ分類する（Conventional Commits形式を前提とする。コミットメッセージ規約は documents/development/coding-rules/common-rules.md Section 1 を参照）：
| Type | カテゴリ | CHANGELOG セクション |
|---|---|---|
feat: |
新機能 | Added |
fix: |
バグ修正 | Fixed |
refactor: / perf: |
変更 | Changed |
docs: |
ドキュメント | Documentation |
test: / chore: / style: |
その他 | Other (CHANGELOGには含めない) |
Step 3: CHANGELOG.md の更新
Keep a Changelog 形式に準拠する。
CHANGELOG.md がなければ新規作成、あれば先頭に追記する。
フォーマット
# Changelog
## [X.Y.Z] - YYYY-MM-DD
### Added
- feat: コミットからの機能追加一覧
### Fixed
- fix: コミットからのバグ修正一覧
### Changed
- refactor/perf: コミットからの変更一覧
### Documentation
- docs: コミットからのドキュメント変更一覧
ルール:
- 空のセクションは含めない（例: fix コミットがなければ Fixed セクションは省略）
- コミットメッセージの type プレフィックスは除去してエントリに記載
- Issue番号やPR番号がある場合はリンクとして含める
Step 4: リリースノート生成
GitHub Releases に投稿可能な形式で生成する。
フォーマット
## What's Changed
### New Features
- 機能1の説明 (#PR番号)
- 機能2の説明 (#PR番号)
### Bug Fixes
- 修正1の説明 (#PR番号)
### Other Changes
- その他の変更
**Full Changelog**: https://github.com/[owner]/[repo]/compare/[前回タグ]...[新タグ]
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 · 147 lines · 30 tokens per session scan A 16a2dd0c00eb
generate-docs is a skill published in the GitHub repository Crearize/ai-dev-helm (4 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 1,169 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.