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/jujunjun110/product-starter/fix-errornpx skills add jujunjun110/product-starter --skill fix-errorgit clone --depth 1 https://github.com/jujunjun110/product-starterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jujunjun110/product-starter/fix-error)<a href="https://agentmods.dev/skills/jujunjun110/product-starter/fix-error"><img src="https://agentmods.dev/badge/skills/jujunjun110/product-starter/fix-error.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.00464 |
| Opus 5 | $0.00018 | $0.00232 |
| Sonnet 5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
fix-error 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 today.
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
エラー修正スキル
ユーザーがエラーメッセージを貼り付けて「直して」と指示したときに適用する。
手順
- エラーメッセージを解析 — エラーの種類と発生箇所を特定
- 原因を特定 — コードを読んで根本原因を調査
- 修正を実施 — アーキテクチャルールに違反しない形で修正
- 検証 —
pnpm verifyで全チェックがパスすることを確認
よくあるエラーと対処
型エラー（TypeScript）
tsc --noEmitで確認- 型の不一致を修正。
anyは使わない
依存方向違反（dependency-cruiser）
pnpm depcruiseで確認- 依存方向:
presentation → application → domain ← infrastructure - application から infrastructure を直接 import している場合 → Gateway interface 経由に修正
- presentation/loaders,actions から domain,infrastructure を import している場合 → composition 経由に修正
Prisma エラー
- スキーマ変更後に
pnpm --filter webapp prisma generateを忘れている場合が多い - マイグレーションが必要な場合は
pnpm db:migrate
lint エラー
pnpm lint:fixで自動修正
ルール
- 修正時もアーキテクチャルール（依存方向、命名規約）を守る
- 修正後は必ず
pnpm verifyを実行 - エラーの根本原因を修正する（場当たり的な回避策は避ける）
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.
- today First seen · 40 lines · 36 tokens per session scan A c4ac6016ea7f
fix-error is a skill published in the GitHub repository jujunjun110/product-starter (17 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 464 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-09-03.
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…