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 skills add j5ik2o/okite-ai --skill error-handlinggit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/error-handling)<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/error-handling"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/error-handling.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.1 | $0.00174 | $0.01112 |
| Opus 5 | $0.00087 | $0.00556 |
| Sonnet 5 | $0.00035 | $0.00222 |
| Haiku 4.5 | $0.00017 | $0.00111 |
Grade A, and why
error-handling 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- error-handling — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
エラーハンドリング
回復可能性を基準にしたエラーハンドリング設計を支援する。
基本方針
ドメインロジック（ビジネスルール）では Either/Result 型を採用する。
- ドメイン層のエラーは呼び出し元が判断すべき → 型で明示
- 例外は制御フローではなく、本当の異常事態に限定
- 戻り値の型を見るだけでエラーの可能性が分かる設計
判断フロー
エラー発生
↓
回復可能か？
├─ YES → Either/Result型で表現
└─ NO → 例外/panicで即座に停止
| 回復可能 | 回復不能 |
|---|---|
| ビジネスルール違反 | 引数の不正 (IllegalArgumentException) |
| 外部システムエラー | 状態の矛盾 (IllegalStateException) |
| 権限不足・リソース競合 | 到達不可コード (unreachable) |
回復可能なエラー
Either/Result型で表現し、呼び出し元に判断を委ねる。
// TypeScript - neverthrow
function findUser(id: string): Result<User, UserError> {
if (!isValidId(id)) return err({ type: 'VALIDATION_FAILED', field: 'id' });
return repository.find(id)
? ok(user)
: err({ type: 'NOT_FOUND', userId: id });
}
回復不能なエラー
プログラムの前提条件違反は即座に停止。
// 引数の不正 → IllegalArgumentException 相当
if (order === null) throw new Error('order must not be null');
// 状態の矛盾 → IllegalStateException 相当
if (order.status === 'COMPLETED' && order.items.isEmpty())
throw new Error('completed order must have items');
// 到達不可コード → unreachable
default: throw new Error(`unreachable: ${status}`);
推奨ライブラリ
| 言語 | ライブラリ | 選択基準 |
|---|---|---|
| TypeScript | neverthrow |
Result のみで十分な場合（軽量・シンプル） |
| TypeScript | fp-ts |
関数型全般を使う場合（Option, Task, IO, Reader 等） |
| JavaScript | neverthrow |
TypeScript と同様 |
| Rust | 標準 Result<T, E> |
常にこれを使用。エラー定義には thiserror |
| Go | 標準 (T, error) |
Go らしいシンプルなコードを書く場合 |
| Go | samber/mo |
Result/Either でチェーン処理したい場合 |
| Scala | 標準 Either[L, R] |
標準で十分。cats は大規模 FP 向け |
| Java | vavr.io Either |
関数型コレクションも使うなら vavr 一択 |
| Python | returns (dry-python) |
本番環境向け。型アノテーション充実 |
| Python | result |
軽量。Rust ライクなシンプルな API |
詳細ガイドライン
全言語の実装パターン、エラー型設計の詳細は references/guidelines.md を参照。
関連スキル（併読推奨）
このスキルを使用する際は、以下のスキルも併せて参照すること：
error-classification: エラーの分類（Error, Defect, Fault, Failure）に基づく処理方式の選択domain-building-blocks: ドメイン操作におけるResult/Eitherの適用repository-design: リポジトリのエラー処理パターン（同期・非同期）
What ships with it
1 file 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.
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.
- 7d ago First seen · 94 lines · 174 tokens per session scan A 9578dcf9efc5
error-handling is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 174 tokens to every session and 1,112 once invoked, about $0.0009 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-01.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.