submit-solution

submit-solution is a skill for Claude Code, Codex from anthropics/cwc-workshops. It costs 50 tokens per session (725 once invoked), scanned A, original, Apache-2.0.

A submission guide for a workshop attendee who has finished decomposing a StockPilot coding task. It covers collecting feedback, checking the code changes, and opening a pull request, which is a proposed change submitted for review.

In plain words
What is it for?
It is for answering the workshop questions, reviewing the changed starter file, checking the latest evaluation score, and preparing the pull request.
Why use it?
It helps package the attendee's solution and feedback in the format workshop facilitators expect before sharing it.

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/anthropics/cwc-workshops/submit-solution
Any agent
npx skills add anthropics/cwc-workshops --skill submit-solution
Clone the repo
git clone --depth 1 https://github.com/anthropics/cwc-workshops

Made for: Claude Code, 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.

agentmods badge for submit-solution

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/cwc-workshops/submit-solution.svg)](https://agentmods.dev/skills/anthropics/cwc-workshops/submit-solution)
Your own site
<a href="https://agentmods.dev/skills/anthropics/cwc-workshops/submit-solution"><img src="https://agentmods.dev/badge/skills/anthropics/cwc-workshops/submit-solution.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 725 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00050 $0.00725
Opus 5 $0.00025 $0.00362
Sonnet 5 $0.00010 $0.00145
Haiku 4.5 $0.00005 $0.00072

Measured 4d ago against content hash 26e9a8668869, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

submit-solution 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 4d 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.

agent-decomposition/.claude/skills/submit-solution/SKILL.md · 92 lines

How it starts

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

Submit your StockPilot solution

You're helping a workshop attendee package up their agents/starter/agent.py decomposition and open a PR. The PR is how facilitators see what approaches people took, and the description doubles as the workshop feedback form.

Step 1 — Ask about their experience first

Before touching git, ask these three questions (use AskUserQuestion or just conversational):

  1. Which subagent approach did you go with for cycle 3? (callable_agents / spawn_subagent / inline / something else)
  2. What was the hardest part of the workshop? (a specific cycle, a concept, the tooling, the timing)
  3. One thing you'd change about it?

Hold onto their answers — they go in the PR body.

Step 2 — Show them what they're submitting

git diff main -- agent-decomposition/agents/starter/agent.py

Walk through the diff briefly: which tools they dropped, which skills they enabled, which subagent approach they wired. If the diff is empty, they haven't edited starter — ask if they worked in a different file.

Also grab their final eval score:

ls -t evals/reports/*/starter.json | head -1 | xargs cat | python -c "import json,sys; d=json.load(sys.stdin); print(f'{d[\"score\"]:.0%}')"

Step 3 — Commit and push

git checkout -b solution/<their-name-or-handle>
git add agent-decomposition/agents/starter/agent.py
git commit -m "Workshop solution: <subagent approach>, <score>%"
git push -u origin solution/<their-name-or-handle>

Ask for their name/handle if you don't have it. If they don't have push rights to anthropics/cwc-workshops, have them fork first (gh repo fork --clone=false) and push to their fork.

Step 4 — Open the PR with feedback in the body

gh pr create --title "Workshop solution — <name>" --body-file -

PR body template (fill from step 1 + step 2):

## My decomposition

- Subagent approach: <callable_agents | spawn_subagent | inline | other>
- Final eval score: <NN>%
- Tools I dropped: <list>
- Skills I enabled: <list>

## Workshop feedback

**Hardest part:** <their answer>

**One thing I'd change:** <their answer>

**Anything else:** <free text — leave blank if nothing>

Read the full file on GitHub · 92 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. 4d ago First seen · 92 lines · 50 tokens per session scan A 26e9a8668869

Subscribe to this mod's changes

submit-solution is a skill published in the GitHub repository anthropics/cwc-workshops (2,043 stars, last pushed 7d ago), licensed Apache-2.0. It adds 50 tokens to every session and 725 once invoked, about $0.0003 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-30.

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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens