code-execution

A coding workflow for implementing a small, predefined software task from a JSON file. It reads the task requirements, project standards, and related code before making changes.

In plain words
What is it for?
Use it to build a feature or fix from acceptance criteria, update the required files or endpoints, and check the result against project standards.
Why use it?
It reduces missed requirements and inconsistent code by giving implementation work a fixed checklist and review process.

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/darrenhinde/openagentscontrol/code-execution
Any agent
npx skills add darrenhinde/OpenAgentsControl --skill code-execution
Clone the repo
git clone --depth 1 https://github.com/darrenhinde/OpenAgentsControl

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,080 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.00027 $0.01080
Opus 5 $0.00014 $0.00540
Sonnet 5 $0.00005 $0.00216
Haiku 4.5 $0.00003 $0.00108

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

Security

Grade A, and why

code-execution 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 2d 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.

plugins/claude-code/skills/code-execution/SKILL.md · 174 lines

How it starts

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

Code Execution

Overview

Execute coding subtasks with self-review and quality validation. Runs in isolated coder-agent context with pre-loaded standards.

Announce at start: "I'm using the code-execution skill to implement [subtask title]."

The Process

Step 1: Read Subtask JSON

Load the subtask file specified in $ARGUMENTS:

Read: .tmp/tasks/{feature}/subtask_{seq}.json

Extract:

  • title — What to implement
  • acceptance_criteria — What defines success
  • deliverables — Files/endpoints to create
  • context_files — Standards to apply
  • reference_files — Existing code to study

Step 2: Load Context Files

Read each file in context_files:

Read: .opencode/context/core/standards/code-quality.md
Read: .opencode/context/core/standards/security-patterns.md

Understand:

  • Project coding standards
  • Naming conventions
  • Security patterns
  • Code quality requirements

Step 3: Load Reference Files

Read each file in reference_files:

Read: src/middleware/auth.middleware.ts

Study:

  • Existing patterns
  • Code structure
  • Conventions in use

Step 4: Update Status to In Progress

Edit subtask JSON:

"status": "in_progress",
"agent_id": "coder-agent",
"started_at": "2026-02-16T00:00:00Z"

Step 5: Implement Deliverables

For each deliverable:

  • Create or modify the specified file
  • Follow acceptance criteria EXACTLY
  • Apply standards from context_files
  • Use patterns from reference_files
  • Write clean, modular, functional code

Step 6: Run Self-Review (MANDATORY)

Type & Import Validation:

  • ✅ Function signatures match usage
  • ✅ All imports/exports exist
  • ✅ No missing type annotations
  • ✅ No circular dependencies

Anti-Pattern Scan:

grep "console.log" deliverables  # NO debug statements
grep "TODO\|FIXME" deliverables  # NO unfinished work
grep "api[_-]key\|secret" deliverables  # NO hardcoded secrets

Acceptance Criteria Check:

  • Re-read acceptance_criteria array
  • Confirm EACH criterion met
  • Fix unmet criteria before proceeding

Read the full file on GitHub · 174 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. 2d ago First seen · 174 lines · 27 tokens per session scan A 3bb426c9e8ad

Subscribe to this mod's changes

code-execution is a skill published in the GitHub repository darrenhinde/OpenAgentsControl (4,799 stars, last pushed 18d ago), licensed MIT. It adds 27 tokens to every session and 1,080 once invoked, about $0.0001 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

azure-openai-to-responses

Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API…

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

knowledge-base

Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…

wonderwhy-er/DesktopCommanderMCP · 112 tokens

peer-review

Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…

xintaofei/codeg · 71 tokens

statistical-power

Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…

xintaofei/codeg · 190 tokens

build-teaql-app

Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…

teaql/teaql-agent-kit · 112 tokens

dd-code-generation

Use pup CLI for immediate Datadog operations or generate code for integration into applications.

DataDog/pup · 16 tokens