ce:work-beta

ce:work-beta is a skill for Claude Code from gvkhosla/compound-engineering-pi. It costs 36 tokens per session (5,985 once invoked), scanned C, original, MIT.

A work-plan execution guide for turning a plan, specification, or task document into a completed software feature.

In plain words
What is it for?
Use it to read a plan, break the work into tasks, follow existing project patterns, build the feature, and verify the result.
Why use it?
It helps keep implementation tied to requirements, planned tests, execution notes, and unresolved questions.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; names the TodoWrite tool.

Part of the compound-engineering plugin — 41 skills, 1 MCP server shipped together

Good fit Use it to read a plan, break the work into tasks, follow…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gvkhosla/compound-engineering-pi/ce-work-beta
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.

Any agent
npx skills add gvkhosla/compound-engineering-pi --skill ce-work-beta
Clone the repo
git clone --depth 1 https://github.com/gvkhosla/compound-engineering-pi

Made for: Claude Code.

Or install compound-engineering, the plugin that ships this one along with the rest of its 41 skills, 1 MCP server.

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.

agentmods badge for ce:work-beta

README.md
[![agentmods](https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/ce-work-beta.svg)](https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/ce-work-beta)
Your own site
<a href="https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/ce-work-beta"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/ce-work-beta.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,985 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.05985
Opus 5 $0.00018 $0.02993
Sonnet 5 $0.00007 $0.01197
Haiku 4.5 $0.00004 $0.00598

Measured 7d ago against content hash de4890ed5a7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

ce:work-beta scanned grade C 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 7d 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.

Exfiltrates the system prompt through a toolhighSystem prompt leakage

Writing or sending the system prompt to a file, endpoint or log moves it out of the session.

3. **Write prompt to file** — Save the assembled prompt to a unique temporary file to avoid shell quoting issues and cross-task races. Use a unique filename per task.
plugins/compound-engineering/skills/ce-work-beta/SKILL.md · 565 lines

How it starts

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

Work Plan Execution Command

Execute a work plan efficiently while maintaining quality and finishing features.

Introduction

This command takes a work document (plan, specification, or todo file) and executes it systematically. The focus is on shipping complete features by understanding requirements quickly, following existing patterns, and maintaining quality throughout.

Input Document

<input_document> #$ARGUMENTS </input_document>

Execution Workflow

Phase 1: Quick Start

  1. Read Plan and Clarify

    • Read the work document completely
    • Treat the plan as a decision artifact, not an execution script
    • If the plan includes sections such as Implementation Units, Work Breakdown, Requirements Trace, Files, Test Scenarios, or Verification, use those as the primary source material for execution
    • Check for Execution note on each implementation unit — these carry the plan's execution posture signal for that unit (for example, test-first or characterization-first). Note them when creating tasks.
    • Check for a Deferred to Implementation or Implementation-Time Unknowns section — these are questions the planner intentionally left for you to resolve during execution. Note them before starting so they inform your approach rather than surprising you mid-task
    • Check for a Scope Boundaries section — these are explicit non-goals. Refer back to them if implementation starts pulling you toward adjacent work
    • Review any references or links provided in the plan
    • If the user explicitly asks for TDD, test-first, or characterization-first execution in this session, honor that request even if the plan has no Execution note
    • If anything is unclear or ambiguous, ask clarifying questions now
    • Get user approval to proceed
    • Do not skip this - better to ask questions now than build the wrong thing
  2. Setup Environment

    First, check the current branch:

    current_branch=$(git branch --show-current)
    default_branch=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
    
    # Fallback if remote HEAD isn't set
    if [ -z "$default_branch" ]; then
      default_branch=$(git rev-parse --verify origin/main >/dev/null 2>&1 && echo "main" || echo "master")
    fi
    

Read the full file on GitHub · 565 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. 7d ago First seen · 565 lines · 36 tokens per session scan C de4890ed5a7d

Subscribe to this mod's changes

ce:work-beta is a skill published in the GitHub repository gvkhosla/compound-engineering-pi (51 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 5,985 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (exfiltrates the system prompt through a tool). 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

codex-claude-worker

Translate natural-language user requests into bounded Claude Code worker tasks while Codex or ChatGPT remains the supervisor. Use when the user gives an ordinary prompt and wants Codex to clarify scope, choose a safe work boundary, generate a worker prompt, approve or defer worker execution, read run summaries and…

zhuzai-2007/claude-code-mcp-harness · 86 tokens

write-swift

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know…

wangmiaozero/pi-harness · 107 tokens

emil-design-eng

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

wangmiaozero/pi-harness · 35 tokens

source-research

Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, needs implementation details with source code references, wants to understand why something was changed, or needs authoritative answers backed by actual code. Excels at navigating large…

aretw0/agents-lab · 71 tokens

apple-design

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…

wangmiaozero/pi-harness · 80 tokens

provider-model-discovery

Descobre e seleciona modelos de providers LLM de forma report-only: inventário read-only de modelos, docs oficiais, quota/billing/rate gates e shortlist para canary protegido. Use antes de adicionar providers, escolher modelos ou migrar monitores/roteamento.

aretw0/agents-lab · 60 tokens