execute

A coding skill that carries out an approved implementation plan in the existing project. It follows the project’s conventions, records progress, and updates related work tracking.

In plain words
What is it for?
It is for implementing a completed MiniPRD, a small product requirements document, after the plan has been finalized.
Why use it?
It helps prevent an agent from improvising beyond the agreed plan or losing track of changes as it edits code.

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/tjmustard/hypergraph-coding-agent-framework/hyper-execute
Any agent
npx skills add tjmustard/Hypergraph-Coding-Agent-Framework --skill hyper-execute
Clone the repo
git clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-Framework

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 985 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.00038 $0.00985
Opus 5 $0.00019 $0.00492
Sonnet 5 $0.00008 $0.00197
Haiku 4.5 $0.00004 $0.00098

Measured yesterday against content hash 61aad00cdfe9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute 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 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.

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.

.agents/skills/hyper-execute/SKILL.md · 72 lines

How it starts

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

Execute

This skill implements a plan precisely, minimally, and in full — adhering to existing conventions, updating progress tracking, and ensuring the hypergraph is kept in sync after every modification.

When to use this skill

  • When the user has a compiled MiniPRD_*.md in spec/compiled/ and is ready to build.
  • When the user explicitly runs /hyper-execute or asks to "implement the plan."
  • After /hyper-resolve has compiled the final MiniPRDs and the workspace has been archived.

How to use it

  1. Memory Check

    • Read .agents/memory/activeContext.md before anything else.

    • Check whether the target MiniPRD is listed as complete or already audited.

    • If the MiniPRD is marked complete or audited: HALT. Display the warning, then use AskUserQuestion:

      ⚠️ [MiniPRD name] appears already complete per activeContext.md.
      Run /hyper-audit to archive it, or move it manually:
        mv spec/compiled/[MiniPRD].md spec/archive/[MiniPRD]_AUDITED.md
      
      Confirm you want to re-implement it?
      
      - Option A: Yes, re-implement — proceed even though it appears done
      - Option B: No, stop — I will archive or review it instead
      
  2. Read the MiniPRD

    • Read the target MiniPRD_*.md from spec/compiled/.

    • Confirm a Confidence Score (1–10) against the MiniPRD's "Confidence Mandate" section. If below 9, list the clarifying questions, then use AskUserQuestion:

      Confidence is [N]/10. How do you want to proceed?
      
      - Option A: Answer my questions — provide clarifications so I can proceed
      - Option B: Proceed anyway — accept the risk and implement with current information
      - Option C: Stop — halt until the MiniPRD is revised
      

2.5. Codebase Orientation (Haiku Sub-Agent)

  • Before implementing, launch a read-only sub-agent to pre-load all relevant file contents:
    • Use the Agent tool with subagent_type: "general-purpose" and model: "haiku"
    • Prompt the sub-agent: "Read spec/compiled/[MiniPRD filename] in full. From the Implementation Plan task list, identify every file path that must be created or modified. For each file that already exists in the codebase, read its full content and return it verbatim. For new files, list the path and expected purpose only. Return a structured report mapping file paths to their current content."
  • Wait for the sub-agent result before proceeding to Step 3.
  • Use the returned file contents as your working context for implementation.
  • Fallback: If the sub-agent returns an error or empty result, proceed to Step 3 and read files directly as normal.
  • Do not re-read files the sub-agent already returned unless you need to verify a specific line.

Read the full file on GitHub · 72 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 · 72 lines · 38 tokens per session scan A 61aad00cdfe9

Subscribe to this mod's changes

execute is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 985 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

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

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