grace-execute

grace-execute is a skill for Claude Code, Codex from osovv/grace-marketplace. It costs 31 tokens per session (706 once invoked), scanned A, original, MIT.

A tool for carrying out an approved GRACE 4 change plan. GRACE plans describe planned code changes, while the tool checks the project before, during, and after those changes.

In plain words
What is it for?
Use it to execute GRACE change plans in sequential or parallel-safe mode, run the required `grace lint` checks, and apply durable `.grace` changes centrally after the work is verified.
Why use it?
It helps apply planned changes safely by checking the starting state, validating the intended result, and handling recovery when work was only partly completed.

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 grace plugin — 15 skills shipped together

Good fit Use it to execute GRACE change plans in sequential or parallel-safe mode, run the required grace lint checks, and apply durable .grace changes centrally after the work is verified.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/osovv/grace-marketplace/grace-execute
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 osovv/grace-marketplace --skill grace-execute
Clone the repo
git clone --depth 1 https://github.com/osovv/grace-marketplace

Made for: Claude Code, Codex.

Or install grace, the plugin that ships this one along with the rest of its 15 skills.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/osovv/grace-marketplace/grace-execute/github.svg)](https://agentmods.dev/skills/osovv/grace-marketplace/grace-execute)
Your own site
<a href="https://agentmods.dev/skills/osovv/grace-marketplace/grace-execute"><img src="https://agentmods.dev/badge/skills/osovv/grace-marketplace/grace-execute/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 grace-execute

Your own site · 80×15
<a href="https://agentmods.dev/skills/osovv/grace-marketplace/grace-execute"><img src="https://agentmods.dev/badge/skills/osovv/grace-marketplace/grace-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 706 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00031 $0.00706
Opus 5 $0.00015 $0.00353
Sonnet 5 $0.00006 $0.00141
Haiku 4.5 $0.00003 $0.00071

Measured 9d ago against content hash 2754d87fc413, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

grace-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 9d 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/grace/skills/grace/grace-execute/SKILL.md · 44 lines

What it actually says

<assertion_commands>

  • Active-baseline preflight before observed writes: grace lint --path PROJECT --assertions current
  • Selected baseline: grace lint --path PROJECT --change C-ID --assertions baseline (add --run-commands when the baseline declares MustPassCommand)
  • Selected target without commands: grace lint --path PROJECT --change C-ID --assertions target
  • Selected target with command evidence: grace lint --path PROJECT --change C-ID --assertions target --run-commands
  • Final end-state validation: grace lint --path PROJECT --change C-ID --assertions final (add --run-commands when the target declares MustPassCommand)
  • Parallel preflight: grace lint --path PROJECT --parallel-preflight </assertion_commands>

<mode_selection> Wait for explicit sequential or parallel-safe choice. Parallel-safe requires the explicit preflight to pass. Workers never mutate approved plans; durable .grace changes are applied centrally after observed work verifies. </mode_selection>

<recovery_decision_table> | state | required action | | clean-to-start | Run selected baseline, then execute tasks. | | partial-observed-writes | Inspect the declared observed scope and ask whether to resume or revert. | | durable-state-changed | Hard stop; supersede and replan. Approved assertions are immutable. | | target-already-satisfied | Run final end-state validation, opted-in command evidence when declared, durable reconciliation, and ask for explicit apply confirmation. | | unsafe-unknown-drift | Hard stop and report unexplained files. | </recovery_decision_table>

<execution_rules>

  1. Run the selected baseline before implementation, including explicit --run-commands when its assertions declare MustPassCommand.
  2. Execute one dependency-ready task or one verified parallel-safe batch at a time.
  3. Run each task's acceptance and verification immediately.
  4. Apply approved durable context, graph, and verification changes centrally.
  5. Reconcile durable state, run leaf plan gates, then run selected --assertions final as the outermost lifecycle gate, including --run-commands when MustPassCommand is declared. Final mode performs full project lint, evaluates the selected target, keeps unrelated approved baselines active, and does not re-evaluate the selected plan's superseded baseline.
  6. Ask for explicit apply confirmation after fresh end-state evidence passes.
  7. Only then set spec and plan to applied and archive the complete bundle.
  8. Never edit approved assertions/scopes/tasks in place, bypass stale evidence, or continue through unknown drift. </execution_rules>
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. 9d ago First seen · 44 lines · 31 tokens per session scan A 2754d87fc413

Subscribe to this mod's changes

grace-execute is a skill published in the GitHub repository osovv/grace-marketplace (240 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 706 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-30.

Related

Other skills, from other repositories

loop-engineering

Use when the user wants to "set up a loop", build a self-running or run-until-done agent, automate a recurring engineering task (triage, keep-CI-green, dependency bumps, backlog burndown), or stop hand-prompting an agent turn by turn. Sets up an autonomous engineering loop in the current project. It discovers work…

sxivansx/loop-engineering · 105 tokens

product-discovery

File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or…

theagenticguy/erpaval · 242 tokens

meta-prompt-optimizer

Audit and rewrite prompts against Claude Opus 4.7 instruction-following best practices. Produces a scored audit plus a rewritten prompt. Use when the user asks to audit, review, critique, rewrite, improve, optimize, tighten, score, fix, migrate, or draft a prompt — including system prompts, CLAUDE.md files, Claude…

theagenticguy/erpaval · 230 tokens

product-strategy

File-first orchestrator for business and product strategy frameworks. Frames the challenge with a CPO / CSO / VP Design role, spawns parallel framework agents (Rumelt kernel + Crux, Wardley Maps, Minto Pyramid as thinking structure, Working Backwards PR-FAQ as discovery artifact), synthesizes outputs into one strategy…

theagenticguy/erpaval · 216 tokens

all-hands

Convene the relevant SpecRoute implementation agents to plan, collaborate, implement, and review a piece of work end-to-end. Engages only the specialists the work actually touches, runs autonomously through planning into implementation and review, and accepts free-text work or a path to a PRD / spec / issue file.…

Enovatr-Labs/SpecRoute · 106 tokens

doc-currency-check

Audit SpecRoute's documentation for staleness against reality - vendor facts, version anchors, dates written in the wrong tense, counts that no longer match disk, and claims mirrored inconsistently across the four vendor-matrix copies. Use before a release, after any vendor ships a breaking change, or on a scheduled…

Enovatr-Labs/SpecRoute · 106 tokens