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/prd)<a href="https://agentmods.dev/commands/ooiyeefei/ccc/prd"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/prd/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/prd"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/prd.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.00008 | $0.00498 |
| Opus 5.5 | $0.00003 | $0.00199 |
| Sonnet 5.5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
prd 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
PRD Generation
Generate Product Requirements Document for $ARGUMENTS and create GitHub Issue.
Prerequisites
-
Check GitHub CLI:
gh auth status -
Check for existing context in:
.pm/gaps/*.md(for WINNING score).pm/competitors/*.md(for competitive evidence)
Process
Use the prd-generator agent for comprehensive PRD:
-
Gather Context
- Load gap analysis data for $ARGUMENTS if exists
- Load competitor implementations
- Ask user for additional requirements if needed
-
Deduplication Check
gh issue list --search "$ARGUMENTS" --label "pm:feature-request" --json number,titleIf similar issue exists (>70% match):
- Show existing issue
- Ask: "Update existing or create new?"
-
Generate PRD with sections:
- Problem Statement
- User Stories
- Competitive Analysis
- Requirements (Functional, Non-Functional)
- Acceptance Criteria (P0/P1/P2)
- Edge Cases
- Out of Scope
- Technical Considerations
- Success Metrics
-
Save PRD
- Create
.pm/prds/directory if not exists - Save to
.pm/prds/[feature-slug].md
- Create
-
Create GitHub Issue
gh issue create \ --title "Feature: $ARGUMENTS" \ --body "$(cat .pm/prds/[feature-slug].md)" \ --label "pm:feature-request" \ --label "[winning-label]" \ --label "[priority-label]" -
Update Tracking
- Save issue reference to
.pm/requests/[issue-number].md - Update
.pm/cache/last-updated.json
- Save issue reference to
-
Return Results
- PRD file location
- GitHub Issue URL
- Next steps:
/speckit.specify #[issue-number]
If gh CLI Unavailable
Output PRD formatted for manual GitHub issue creation.
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 · 76 lines · 8 tokens per session scan A 3b810f504956
prd is a command published in the GitHub repository ooiyeefei/ccc (496 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 498 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.