What is ensemble-implement?

An implementation workflow for the CC Workshop desktop app, which uses React/TypeScript on the frontend and Rust on the backend. It finds a suitable Linear issue, develops the change with TDD—writing tests before the code—and submits a pull request after checks.

Use it to implement a bug fix or feature from the CC Workshop Linear project, run the required tests and code checks, and create a pull request.

It connects issue selection, coding, testing, and delivery into one process. This reduces the manual coordination needed to turn an approved task into a reviewed change.

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-implement/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-implement/github.svg)](https://agentmods.dev/skills/o0000-code/cc-workshop/cc-workshop-implement)

Your own site

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

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

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

Security scan B 1 finding. 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.00072	$0.01994
Opus 5.5	$0.00029	$0.00798
Sonnet 5.5	$0.00014	$0.00399
Haiku 4.5	$0.00007	$0.00199

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

Security

Grade B, and why

ensemble-implement scanned grade B with 1 finding 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- [ ] Clippy passes without warnings

.codex/skills/cc-workshop-implement/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CC Workshop Issue Implementation

Overview

Autonomously discover, claim, implement, and deliver a single agent-ready Issue from the CC Workshop Linear project. This skill covers the full cycle: query Linear for work, write code via TDD across React frontend and Rust backend, verify all checks, and submit a Pull Request.

Project Context

Frontend: React 18 + TypeScript 5.9 + Tailwind CSS 4 + Zustand 5
Backend: Tauri 2.9 + Rust (edition 2021)
Testing: Vitest + @testing-library/react (frontend), cargo test (backend)
Repo: https://github.com/O0000-code/CC-Workshop.git

Read AGENTS.md for the full project conventions before starting.

Workflow

1) Discover Agent-Ready Issues

CRITICAL RULES:

You MUST actually call the MCP tools. Do NOT fabricate or hallucinate tool call results.
If an MCP tool call fails, report the failure honestly. Do NOT pretend it succeeded.
Use list_teams to find your team ID dynamically. NEVER hardcode team IDs.
Use list_projects to find the "CC Workshop" project. NEVER hardcode project IDs.
Use list_issue_labels to find label IDs dynamically. NEVER hardcode label IDs.

Query Linear for issues ready for agent implementation:

Use list_teams to get the team ID.
Use list_projects to find the "CC Workshop" project ID.
Use list_issue_labels to find the IDs for labels: agent-ready and CC Workshop.
Use list_issues with filters to find issues that have the agent-ready label AND belong to the CC Workshop project.
Sort results by priority (1=Urgent is highest, 4=Low is lowest).
Select the single highest-priority issue.

If no agent-ready issues are found: report "No pending agent-ready issues in CC Workshop" and exit immediately. Do NOT proceed further.

2) Read the Issue

Use get_issue to fetch the full Issue details of the selected issue.
Read the Description and all comments carefully.
Use list_comments to read all existing comments on the issue.
If any requirements are unclear or ambiguous, use create_comment to ask for clarification and stop execution until answered.

Read the full file on GitHub · 197 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 · 197 lines · 72 tokens per session scan B f821ec33601b

Subscribe to this mod's changes

ensemble-implement is a skill published in the GitHub repository O0000-code/CC-Workshop (18 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 1,994 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Planning TDD Testing desktop-app developer-tools macos mcp

superpowers

Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.

Peiiii/nextclaw · 43 tokens

typescript-eval

Test TypeScript code snippets before persisting as skills.

vellum-ai/vellum-assistant · 14 tokens

TDD 开发纪律助手

A development skill based on TDD, or test-driven development: write or update a test first, make it pass with the smallest code change, then improve the code and check for regressions.

cdavid817/vanehub-ai · 27 tokens

tdd-workflow

A test-first workflow for building features and fixing bugs. TDD, or test-driven development, means writing a failing test for the expected behaviour before implementing the code.

bunhine0452/Ocul-PM · 47 tokens

aetox-forge

Implements tasks and tickets using strict Test-Driven Development (TDD) at pre-agreed seams. Enforces observable external behavior over internal coupling, bans tautological assertions, executes continuous test cycles, and passes completed work through code review with clean context boundaries.

Mikedev115/Aetox · 58 tokens

aetox-testing

ออกแบบกลยุทธ์และแผนทดสอบ, testing pyramid, กลยุทธ์รายชั้น (API, data pipeline, frontend, infra), จัดลำดับ critical path/edge/security บวกวินัย TDD (red-green-refactor) และกับดักเทสต์ที่ควรเลี่ยง ทริกด้วย "ควรเทสต์ยังไง", "test plan", "เขียนเทสต์ให้".

Mikedev115/Aetox · 98 tokens

CC-Workshop: Skill for Codex