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 s977043/PlanGate --skill edgecase-enumerationgit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/s977043/plangate/edgecase-enumeration)<a href="https://agentmods.dev/skills/s977043/plangate/edgecase-enumeration"><img src="https://agentmods.dev/badge/skills/s977043/plangate/edgecase-enumeration.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.00083 | $0.00409 |
| Opus 5 | $0.00042 | $0.00204 |
| Sonnet 5 | $0.00017 | $0.00082 |
| Haiku 4.5 | $0.00008 | $0.00041 |
Grade A, and why
edgecase-enumeration 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.
What it actually says
Edgecase Enumeration
入力の境界値、例外パス、異常系、競合条件などを体系的に列挙する Skill。
カテゴリ
Check
想定 Phase
WF-02 Requirement Expansion
入力
- requirements（機能要件 / 非機能要件）
- 対象のデータ型 / API 仕様 / ユーザー操作フロー
出力
エッジケース一覧:
- 境界値（0 / 最小 / 最大 / オーバーフロー）
- null / 空 / 未定義の扱い
- タイムアウト / 再送 / 部分成功
- 並行アクセス / 競合条件
- 不正な入力 / バリデーション失敗
使い方
- WF-02 で qa-reviewer が呼び出す
- 結果は acceptance-criteria-build とテスト観点設計の入力になる
関連
- Workflow:
docs/workflows/02_requirement_expansion.md（配布対象外。install.sh --claude/ plugin / Codex の 3 経路とも導入先には配置されない。解決できない場合は本 Skill の記述を代替正本とし、「正本<path>を参照できなかった」と明示する） - 連携 Skill: acceptance-criteria-build
- Rule: Rule 2
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 · 43 lines · 83 tokens per session scan A 536206b7d624
edgecase-enumeration is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 409 once invoked, about $0.0004 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
validate
Validate Semantica pipelines, extraction quality, graph schemas, and ontology consistency. Returns structured error/warning checklists. Uses PipelineValidator, PipelineBuilder.validatepipeline(), GraphValidator, and OntologyValidator. Sub-commands: pipeline, step, dependencies, extraction, graph, ontology, performance.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
11-browser-qa
Run post-review browser QA and produce short named videos for a locked happy path and sourced browser edge cases. Use when the user wants concise reviewer evidence for a web journey. Not for API, CLI, automated tests, diff review, or application fixes.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.