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/ooiyeefei/cccWrote 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/commands/ooiyeefei/ccc/gaps)<a href="https://agentmods.dev/commands/ooiyeefei/ccc/gaps"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/gaps/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/commands/ooiyeefei/ccc/gaps"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/gaps.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.00007 | $0.00485 |
| Opus 5.5 | $0.00003 | $0.00194 |
| Sonnet 5.5 | $0.00001 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
gaps 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
Gap Analysis
Identify product gaps and score with WINNING filter.
Prerequisites Check
-
Verify
.pm/product/inventory.mdexists- If missing: "Run
/pm:analyzefirst to create product inventory."
- If missing: "Run
-
Verify
.pm/competitors/*.mdfiles exist- If missing: "Run
/pm:landscapefirst to research competitors."
- If missing: "Run
-
Check staleness in
.pm/cache/last-updated.json- If competitor data >30 days old: Prompt to refresh first
Process
Use the gap-analyst agent for systematic analysis:
-
Sync with GitHub Issues for deduplication:
gh issue list --label "pm:feature-request" --json number,title,body,labels --limit 100Update
.pm/requests/with current issues. -
Load Context
- Read
.pm/product/inventory.md - Read all
.pm/competitors/*.md - Read
.pm/requests/*.md(existing issues)
- Read
-
Identify ALL Gaps
- Features competitors have that we don't
- Features multiple competitors are building (trends)
- Features from user reviews/requests
-
Deduplication Check For each gap, fuzzy match against existing issues:
-
80% match → Mark EXISTING (show linked issue)
- 50-80% → Mark SIMILAR (warn user)
- <50% → Mark NEW (proceed with scoring)
-
-
WINNING Filter Scoring (hybrid):
- Claude suggests: Pain Intensity, Market Timing
- Ask user to score: Execution, Fit, Revenue, Moat
-
Recommendations
- 40-60: FILE (high conviction)
- 25-39: WAIT (monitor)
- 0-24: SKIP
-
Save Analysis
- Save to
.pm/gaps/[YYYY-MM-DD]-analysis.md - Update
.pm/cache/last-updated.json
- Save to
Reference references/winning-filter.md in the product-management skill for scoring criteria.
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 · 61 lines · 7 tokens per session scan A edc4e9dc682f
gaps is a command published in the GitHub repository ooiyeefei/ccc (496 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 485 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.