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.

In plain words
What is it for?
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.
Why use it?
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.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/o0000-code/cc-workshop/cc-workshop-implement
Any agent
npx skills add O0000-code/CC-Workshop --skill cc-workshop-implement
Clone the repo
git clone --depth 1 https://github.com/O0000-code/CC-Workshop

Made for: Claude Code, Codex.

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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.01994
Opus 5 $0.00036 $0.00997
Sonnet 5 $0.00014 $0.00399
Haiku 4.5 $0.00007 $0.00199

Measured yesterday against content hash f821ec33601b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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:

  1. Use list_teams to get the team ID.
  2. Use list_projects to find the "CC Workshop" project ID.
  3. Use list_issue_labels to find the IDs for labels: agent-ready and CC Workshop.
  4. Use list_issues with filters to find issues that have the agent-ready label AND belong to the CC Workshop project.
  5. Sort results by priority (1=Urgent is highest, 4=Low is lowest).
  6. 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.

  1. yesterday 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 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,994 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories

papr-rss

Read, search and triage the user's Papr RSS subscriptions from the shell via the papr CLI. Use when the user wants to catch up on their feeds, find or summarize articles they've subscribed to, check what's unread, star/save articles, subscribe to a new feed, or pull new posts. Triggers on: "what's in my feeds", "any…

l0ng-ai/papr · 113 tokens

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.

web-casa/DeepSeek-Harness-Desktop · 45 tokens

release

Use when the maintainer wants to cut, prepare, or ship a code-by-wire release — e.g. says "bump version", "bump vX.Y.Z", "release it", "ship it", or "cut a release" — whether before the release (preparing the version bump and the changelog PR) or after the bump PR has merged (tagging and publishing).

luojiahai/code-by-wire · 82 tokens

vibeshell

Use the native VibeShell CLI to manage saved SSH servers, persistent sessions, remote commands, SFTP transfers, remote files, and SSH configuration imports without requiring the desktop UI.

veithly/vibeshell · 40 tokens

project-structure

Use when orienting within the Hermes Agent CN Desktop codebase, locating source files, understanding the Tauri+React architecture, finding Rust commands or frontend modules, or navigating the monorepo. Triggers: project structure, 项目结构, where is, 在哪里, codebase overview, 代码概览, repository layout, how is this repo…

Eynzof/Hermes-CN-Desktop · 0 tokens

workspace-dispatch

Autonomous multi-agent mission orchestrator. Decomposes a mission into tasks, spawns sub-agents for each step, reviews output against exit criteria, and chains tasks automatically with retry. State persists to disk so missions survive context loss. Triggered by the Conductor UI or by direct user request.

outsourc-e/clawsuite · 65 tokens