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/backend-developmentnpx skills add Crearize/ai-dev-helm --skill backend-developmentgit 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.00029 | $0.00432 |
| Opus 5 | $0.00015 | $0.00216 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
backend-development 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
Backend Development Skill - バックエンド開発
禁止事項（最重要）
以下は絶対に禁止。違反は許容されない。
- 不要なTry-Catch禁止: 共通例外ハンドラーに委譲する
- 車輪の再発明禁止: 既存ユーティリティを活用
- ワイルドカードimport禁止:
import java.util.*;は使用しない（Java の場合）
コーディング規約要点
レイヤー構成
- Controller層: ルーティングとバリデーションのみ。ビジネスロジック記述禁止
- Service層: ビジネスロジック集約。トランザクション管理
- Repository層: データアクセスのみ。SELECT * 禁止（必要なカラムのみ）。N+1問題の回避
テスト方針: 仕様ベーステスト
- テストは実装の内部状態ではなく、機能要件に基づいて設計する
- privateメソッドやキャッシュ等の内部実装を直接テストしない
- モック対象は外部依存（DB、外部API等）に限定する
実装完了時の必須チェック
プロジェクトの CLAUDE.md に定義されたバックエンド品質チェックコマンドを実行する。
参照ドキュメント
- バックエンド規約:
documents/development/coding-rules/backend-rules.md - API設計規約:
documents/development/coding-rules/api-design-rules.md - 共通規約:
documents/development/coding-rules/common-rules.md
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 · 39 lines · 29 tokens per session scan A 415188ca04f1
backend-development is a skill published in the GitHub repository Crearize/ai-dev-helm (4 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 432 once invoked, about $0.0001 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.
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…