exec

A procedure for implementing one GitHub issue from an agreed plan through its acceptance checks.

In plain words
What is it for?
Use it to create a feature worktree, make small changes, run tests and builds, and prepare a progress update for the issue.
Why use it?
It gives coding work a repeatable loop and helps identify when the requested result is complete or blocked.

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/sequant-io/sequant/exec
Any agent
npx skills add sequant-io/sequant --skill exec
Clone the repo
git clone --depth 1 https://github.com/sequant-io/sequant

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 18,370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00026 $0.18370
Opus 5 $0.00013 $0.09185
Sonnet 5 $0.00005 $0.03674
Haiku 4.5 $0.00003 $0.01837

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

Security

Grade A, and why

exec scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:3000 > /dev/null && echo "✓ Server responding" || echo "✗ Server not responding"
.claude/skills/exec/SKILL.md · 2,041 lines

How it starts

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

Local overrides (read this first). Before following any instruction below, check whether .claude/.local/skills/exec/overrides.md exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor /exec without forking it — overrides.md lives under .claude/.local/, which sequant update and sync never overwrite.

Implementation Command

You are the Phase 2 "Implementation Agent" for the current repository.

Purpose

When invoked as /exec, your job is to:

  1. Take an existing, agreed plan and AC (often created by /spec).
  2. Create a feature worktree for the issue.
  3. Implement the changes in small, safe steps.
  4. Run checks via npm test and, when appropriate, npm run build.
  5. Iterate until the AC appear satisfied or clear blockers are reached.
  6. Draft a progress update for the GitHub issue.

Phase Detection (Smart Resumption)

Before executing, check if this phase has already been completed or if prerequisites are met:

# Check for existing phase markers
phase_data=$(gh issue view <issue-number> --json comments --jq '[.comments[].body]' | \
  grep -o '{[^}]*}' | grep '"phase"' | tail -1 || true)

if [[ -n "$phase_data" ]]; then
  phase=$(echo "$phase_data" | jq -r '.phase')
  status=$(echo "$phase_data" | jq -r '.status')

  # Skip if exec is already completed
  if [[ "$phase" == "exec" && "$status" == "completed" ]]; then
    echo "⏭️ Exec phase already completed. Skipping."
    # Exit early — no work needed
  fi

  # Resume if exec previously failed
  if [[ "$phase" == "exec" && "$status" == "failed" ]]; then
    echo "🔄 Exec phase previously failed. Resuming from failure point."
    # Continue execution — will retry the implementation
  fi
fi

Behavior:

  • If exec:completed → Skip with message
  • If exec:failed → Resume (retry implementation)
  • If spec:completed (no exec marker) → Normal execution
  • If no markers found → Normal execution (fresh start)
  • If detection fails (API error) → Fall through to normal execution

Read the full file on GitHub · 2,041 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 · 2,041 lines · 26 tokens per session scan A 748dad1fed37

Subscribe to this mod's changes

exec is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 18,370 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

agent-estate

Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.

MercuriusDream/agent-estate · 36 tokens

citation-audit

Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports — catching hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations. Use when user says "审查引用", "check citations"…

wanshuiyin/Auto-claude-code-research-in-sleep · 86 tokens

paper-illustration

Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.

wanshuiyin/Auto-claude-code-research-in-sleep · 67 tokens

paper-illustration-image2

Generate publication-quality academic illustrations through a local Codex app-server bridge that uses Codex native image generation. This is a separate experimental alternative to paper-illustration, intended for Claude Code users who want a GPT-image-style renderer without modifying the original skill.

wanshuiyin/Auto-claude-code-research-in-sleep · 59 tokens

experiment-plan

Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after research-refine, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty…

wanshuiyin/Auto-claude-code-research-in-sleep · 80 tokens

paper-writing

Workflow 3: Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.

wanshuiyin/Auto-claude-code-research-in-sleep · 58 tokens