What is ensemble-patrol?

A quality-audit workflow for the CC Workshop Tauri desktop app, which combines a React/TypeScript frontend with a Rust backend. It runs tests, code checks, formatting checks, and records the results.

Use it to check project health, run frontend and backend tests, lint the code, verify TypeScript, run Rust checks, and produce an audit report.

It brings the main health checks into one repeatable review. This helps reveal failing tests, type or lint errors, Rust issues, and formatting problems before changes are delivered.

How O0000-code/CC-Workshop configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to O0000-code/CC-Workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/O0000-code/CC-Workshop/main/.codex/skills/cc-workshop-patrol/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/O0000-code/CC-Workshop

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/o0000-code/cc-workshop/cc-workshop-patrol/github.svg)](https://agentmods.dev/skills/o0000-code/cc-workshop/cc-workshop-patrol)

Your own site

<a href="https://agentmods.dev/skills/o0000-code/cc-workshop/cc-workshop-patrol"><img src="https://agentmods.dev/badge/skills/o0000-code/cc-workshop/cc-workshop-patrol/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/o0000-code/cc-workshop/cc-workshop-patrol"><img src="https://agentmods.dev/badge/skills/o0000-code/cc-workshop/cc-workshop-patrol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,227 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00047	$0.01227
Opus 5.5	$0.00019	$0.00491
Sonnet 5.5	$0.00009	$0.00245
Haiku 4.5	$0.00005	$0.00123

Measured 1mo ago against content hash 5d2dd47cd6ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.codex/skills/cc-workshop-patrol/SKILL.md · 150 lines

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 main to 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 --oneline to list recent commits.
For each commit, review the diff for:
- Unsafe Tauri IPC calls (not using safeInvoke)
- Missing error handling in async functions
- TypeScript any types that should be properly typed
- Rust unwrap() calls that should use proper error handling
- Files exceeding 300 lines
Record any issues found.

Read the full file on GitHub · 150 lines

Changes

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 · 150 lines · 47 tokens per session scan A 5d2dd47cd6ef

Subscribe to this mod's changes

ensemble-patrol is a skill published in the GitHub repository O0000-code/CC-Workshop (18 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,227 once invoked, about $0.0002 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.

Claude Code Testing desktop-app developer-tools macos mcp

swift-testing-pro

Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

jacklandrin/OnlySwitch · 34 tokens

finishing-a-branch

Wrap up finished code work safely: confirm the tests pass, then let the Commander choose to merge it, open a pull request, or keep it for later. Nothing is deleted or overwritten without the Commander's clear go-ahead.

androoAGI/starnet · 52 tokens

receiving-code-review

Handle review feedback on code with care: understand each point, check it against the real code before changing anything, fix what is right, and push back with reasons on what is wrong. Use when review comments arrive.

androoAGI/starnet · 48 tokens

web-app-qa

Test a web app the way a real user would: click through the main flows, try odd inputs, watch for errors, and keep screenshots as proof. You get a bug report ranked by how serious each problem is.

androoAGI/starnet · 49 tokens

verification-before-completion

Never say work is done, fixed or passing without fresh proof: run the check that proves it, read the result, then report what it showed. Use before any claim of success, and before saving, committing or handing work over.