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 Eliyce/paqad-ai --skill edge-case-detectiongit clone --depth 1 https://github.com/Eliyce/paqad-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/eliyce/paqad-ai/edge-case-detection)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/edge-case-detection"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/edge-case-detection/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/edge-case-detection"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/edge-case-detection.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00535 |
| Opus 5 | $0.00007 | $0.00267 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
edge-case-detection 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 10d 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
What It Does
Finds missing failure modes, uncommon paths, and state transitions that would materially affect requirements, design, implementation, or verification if ignored.
Use This When
Use this during planning, design, or review when the work changes user flows, data transitions, or operational behavior and the happy path is already understood.
Inputs
- Read the request, acceptance criteria, and proposed solution first.
- Read canonical docs that describe current states or interfaces for the affected module.
- Read
references/edge-case-categories.mdand the shared coding checklist before producing findings.
Procedure
- Enumerate the primary flow as a baseline.
- Walk every category in
assets/categories.txt(empty, stale, loading, retry, permission, concurrency, rollback, integration, overflow, state-skip) against the request. - Keep only cases that materially change behavior, docs, or verification scope.
- Tie each case to the artifact that absorbs it (requirements, UX states, AC, tests, rollback plan).
- Format per
assets/output.template.md; validate withscripts/lint-output.sh.
Output Contract
- Match
assets/output.template.md:## Edge Cases+ per-case### ...withScenario:,Why It Matters:,Apply To:lines. - When nothing additional is found, output the literal
No Additional Edge Cases(with no other content). - Output must pass
scripts/lint-output.sh(exit 0).
Escalate / Stop Conditions
- Ask when current behavior is undocumented and edge-case expectations depend on product policy.
- Warn when a missing case implies unrecoverable data loss or customer-facing failure.
- Do not add theoretical scenarios that are not credible for the current request.
Resources
references/edge-case-categories.mdscripts/lint-output.shassets/output.template.mdassets/categories.txtruntime/capabilities/coding/checklists/edge-cases-coding.mdagents/openai.yaml
What ships with it
5 files 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.
- 10d ago First seen · 65 lines · 14 tokens per session scan A 4454d4e6d8a2
edge-case-detection is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 535 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.