choose-work-profile

choose-work-profile is a skill for Claude Code, Codex from iamcxa/kc-claude-plugins. It costs 40 tokens per session (1,603 once invoked), scanned A, original, MIT.

A workflow helper for choosing whether a piece of work should be a proof of concept, a pilot, or a production change. A proof of concept tests an idea, a pilot tests it in limited use, and production means delivering it for regular use.

In plain words
What is it for?
Use it before work starts or when new evidence suggests the chosen profile is outdated. It recommends a profile and asks the person approving the work to confirm the choice.
Why use it?
It prevents work from entering a development stage with an unsuitable level of commitment or risk. It also flags an old choice when the audience, lifespan, ownership, or operational commitment has changed.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the kc-dev-flow plugin — 6 skills, 2 agents shipped together

Good fit Use it before work starts or when new evidence suggests the chosen profile is outdated. It recommends a profile and asks the person approving the work to confirm the choice.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iamcxa/kc-claude-plugins/choose-work-profile
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 iamcxa/kc-claude-plugins --skill choose-work-profile
Clone the repo
git clone --depth 1 https://github.com/iamcxa/kc-claude-plugins

Made for: Claude Code, Codex.

Or install kc-dev-flow, the plugin that ships this one along with the rest of its 6 skills, 2 agents.

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 choose-work-profile

README.md
[![agentmods](https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/choose-work-profile/github.svg)](https://agentmods.dev/skills/iamcxa/kc-claude-plugins/choose-work-profile)
Your own site
<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/choose-work-profile"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/choose-work-profile/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.

agentmods 80×15 button for choose-work-profile

Your own site · 80×15
<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/choose-work-profile"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/choose-work-profile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,603 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01603
Opus 5 $0.00020 $0.00801
Sonnet 5 $0.00008 $0.00321
Haiku 4.5 $0.00004 $0.00160

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

Security

Grade A, and why

choose-work-profile 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 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.

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.

kc-dev-flow/skills/choose-work-profile/SKILL.md · 137 lines

How it starts

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

Choose Work Profile

Select the lifecycle before loading its working contract. The Captain chooses; this skill has recommendation and question authority only.

Resolve the choice

Ask first: Could credible negative evidence cancel or materially change the next commitment this item asks the Captain to accept? Yes recommends POC. No compares Pilot and Production using the existing delivery-risk boundaries.

Read the exact work item and its ## Work profile receipt. A Pilot or Production receipt records semantics_unchanged at every working stage from ideation onward, not only at ideation, making the shape's existing observable-semantics declaration machine-readable; the loader refuses any of those stages without it and refuses validation without an equivalence_instrument when it was declared true. Reuse an unchanged supported receipt. A v2 Pilot or Production receipt remains supported; an active v2 POC must finish on its pinned 3.x pair or be Captain re-recorded as v3. Treat any receipt as stale when audience, lifespan, valuable state, mutation boundary, authority need, or operational commitment changes.

An unchanged v1 Pilot or Production receipt already records the Captain's profile choice. Return a mechanical v3 candidate with the same selected, current route, basis, and task-specific obligations. A v1 POC preserves its profile choice but cannot supply the new experiment contract mechanically: ask the Captain to complete the v3 POC fields without reopening the profile choice. Ask for a new selection only when its basis is stale or the selected profile no longer contains the accepted scope.

Choice Route Use when
POC / Exploration (poc-exploration) build -> prove A disposable experiment must prove one real journey and its riskiest assumption.
Pilot / Product slice (pilot-product-slice) shape -> build -> verify-deliver Limited real use creates persistent value and likely iteration.
Production (production) shape -> build -> verify by default; eligible recovery uses build -> verify The scope accepts a production boundary or long-term operational commitment.

Read the full file on GitHub · 137 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 Changed · +7 lines 04ff83a33636
  2. 10d ago First seen · 130 lines · 40 tokens per session scan A a21dbaa9336f

Subscribe to this mod's changes

choose-work-profile is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,603 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens