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 agentmods add commands/ooiyeefei/ccc/syncgit clone --depth 1 https://github.com/ooiyeefei/cccWhat 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 | $0.00007 | $0.00406 |
| Opus 5 | $0.00003 | $0.00203 |
| Sonnet 5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
sync 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 2d 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
GitHub Sync
Sync local .pm/requests/ cache with GitHub Issues for deduplication.
Prerequisites
Check GitHub CLI:
gh auth status
If not authenticated: "Run gh auth login first."
Process
-
Fetch All PM Issues
gh issue list --label "pm:feature-request" --state all --json number,title,body,labels,state,createdAt,updatedAt --limit 200 -
Create/Update Local Cache
- Create
.pm/requests/directory if not exists - For each issue, create/update
.pm/requests/[issue-number].md:
--- github_issue: [number] title: "[title]" state: [open/closed] labels: [list] created: [date] updated: [date] synced: [now] --- [Issue body content] - Create
-
Clean Up Stale Entries
- Remove local files for issues that no longer exist
- Update state for closed issues
-
Update Timestamp
- Update
.pm/cache/last-updated.json:
{ "github_sync": "[ISO timestamp]", "issues_count": [N] } - Update
-
Report Summary
GitHub Sync Complete - Issues synced: [N] - New: [N] - Updated: [N] - Removed: [N] - Last sync: [timestamp]
When to Run
- Automatically suggested on session start if >24 hours since last sync
- Before running
/pm:gapsfor accurate deduplication - After creating issues outside of PM plugin
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.
- 2d ago First seen · 71 lines · 7 tokens per session scan A d87379765eb2
sync is a command published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 406 once invoked, about $0.0000 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.