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 skills/o0000-code/cc-workshop/cc-workshop-patrolnpx skills add O0000-code/CC-Workshop --skill cc-workshop-patrolgit clone --depth 1 https://github.com/O0000-code/CC-WorkshopWhat 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.00047 | $0.01227 |
| Opus 5 | $0.00023 | $0.00613 |
| Sonnet 5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
ensemble-patrol 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC Workshop Tauri Project Patrol
Overview
Perform a comprehensive quality audit on the CC Workshop Tauri 2 desktop application, covering both the React frontend and Rust backend.
Workflow
1) Prepare
- Verify you are in the CC Workshop project directory (
CC Workshop2/). - Run
git fetch origin mainto ensure you have the latest state. - Note the current branch and HEAD commit for the patrol report.
2) Run Frontend Tests
- Execute the frontend test suite:
npm run test - Record: total tests, passed, failed, skipped.
- If any tests fail, classify as "critical" and note the failing test names.
3) Run Backend Tests
- Execute the Rust test suite:
cd src-tauri && cargo test - Record: total tests, passed, failed.
- If any tests fail, classify as "critical".
4) Frontend Linting
- Run ESLint on the frontend source:
npx eslint src/ - Run TypeScript type checking:
npx tsc --noEmit - Record: total warnings, total errors from both tools.
5) Rust Linting
- Run Clippy with strict mode:
cd src-tauri && cargo clippy -- -D warnings - Run format check:
cd src-tauri && cargo fmt -- --check - Record any warnings or formatting issues.
6) Scan for TODO/FIXME/HACK
- Search all source files for tech debt markers:
grep -rn "TODO\|FIXME\|HACK\|XXX" src/ --include="*.ts" --include="*.tsx" grep -rn "TODO\|FIXME\|HACK\|XXX" src-tauri/src/ --include="*.rs" - Count and categorize by type and layer (frontend vs backend).
- Note files with more than 3 markers as high-priority tech debt.
7) Check Recent Changes
- Run
git log --since=24.hours --onelineto list recent commits. - For each commit, review the diff for:
- Unsafe Tauri IPC calls (not using
safeInvoke) - Missing error handling in async functions
- TypeScript
anytypes that should be properly typed - Rust
unwrap()calls that should use proper error handling - Files exceeding 300 lines
- Unsafe Tauri IPC calls (not using
- Record any issues found.
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 · 150 lines · 47 tokens per session scan A 5d2dd47cd6ef
ensemble-patrol is a skill published in the GitHub repository O0000-code/CC-Workshop (18 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,227 once invoked, about $0.0002 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 skills, from other repositories
asc-ppp-pricing
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
asc-apple-ads
Use when managing Apple Ads with asc, including OAuth profiles, ad-account discovery, Platform API v1 campaigns and targeting, reports, assets, recommendations, guarded mutations, raw requests, and Campaign Management API v5 migration.
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-aso-audit
Run an offline ASO audit on canonical App Store metadata under ./metadata and surface keyword gaps using Astro MCP. Use after pulling metadata with asc metadata pull.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…