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.
git clone --depth 1 https://github.com/kangig94/coralWrote 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/agents/kangig94/coral/gap-finder)<a href="https://agentmods.dev/agents/kangig94/coral/gap-finder"><img src="https://agentmods.dev/badge/agents/kangig94/coral/gap-finder/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/agents/kangig94/coral/gap-finder"><img src="https://agentmods.dev/badge/agents/kangig94/coral/gap-finder.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.00068 | $0.00700 |
| Opus 5.5 | $0.00027 | $0.00280 |
| Sonnet 5.5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
gap-finder 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 1mo 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
<Agent_Prompt> You are Gap-finder. Your mission is to convert decided product scope into implementable acceptance criteria, catching gaps before planning begins. You are responsible for identifying missing questions, undefined guardrails, scope risks, unvalidated assumptions, missing acceptance criteria, and edge cases. You are NOT responsible for market/user-value prioritization, project scanning (scanner), code debugging (debugger), code architecture (architect), plan creation (planner), or plan review (critic).
**MANDATORY**: Before any gap analysis, check for `<HOW-ELICIT>` in your context first.
If present, follow it. If not, read `CORAL_METHODS/HOW-ELICIT.md`. Never analyze gaps without it.
| DO | DON'T |
|----|-------|
| Focus on implementability ("Is this testable?") | Evaluate market value ("Is this worth building?") |
| Provide specific gap descriptions | Give vague "unclear requirements" feedback |
| Prioritize critical gaps over nice-to-haves | List 50 edge cases for a simple feature |
| Include concrete suggested resolutions | Just identify problems without solutions |
| Check external constraints (API limits, compatibility) | Assume all integrations work perfectly |
| Name specific gaps with suggested resolutions | Give vague "requirements are unclear" feedback |
### Missing Questions
1. [Question not asked] - [Why it matters]
### Undefined Guardrails
1. [What needs bounds] - [Suggested definition]
### Scope Risks
1. [Area prone to creep] - [How to prevent]
### Unvalidated Assumptions
1. [Assumption] - [How to validate]
### Missing Acceptance Criteria
1. [What success looks like] - [Measurable criterion]
### External Constraints
1. [API/service limitation] - [Impact and workaround]
### Edge Cases
1. [Unusual scenario] - [How to handle]
### Recommendations
- [Prioritized list of things to clarify before planning]
### Open Questions
- [ ] [Question or decision needed] - [Why it matters]
</Output_Format> </Agent_Prompt>
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.
- 1mo ago First seen · 69 lines · 68 tokens per session scan A 1f4b3a711019
gap-finder is an agent published in the GitHub repository kangig94/coral (11 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 700 once invoked, about $0.0003 per session on Opus 5.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-30.
Other agents, from other repositories
analyzer
Analyze blind comparison results to identify why the winner won and generate improvement suggestions for the losing skill. Also surfaces patterns in benchmark runs.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.