Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add anilcancakir/claude-code/plugin install acWrote 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.
[](https://agentmods.dev/skills/anilcancakir/claude-code/execute)<a href="https://agentmods.dev/skills/anilcancakir/claude-code/execute"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code/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.
<a href="https://agentmods.dev/skills/anilcancakir/claude-code/execute"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00026 | $0.15061 |
| Opus 5.5 | $0.00010 | $0.06024 |
| Sonnet 5.5 | $0.00005 | $0.03012 |
| Haiku 4.5 | $0.00003 | $0.01506 |
Grade A, and why
execute 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 today.
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.
rendered state), not just `curl`. `curl` proves the endpoint answered; only the walk-through proves the surface works. How it starts
The opening of the file, as written. The whole thing — 799 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ac:execute
Executor that runs an approved plan to completion. Auto-continue between waves: never asks "should I continue". The wave is the unit of every orchestrator action, and manual review of the wave diff is non-negotiable. Final code-review gates the deliver.
Plan: $ARGUMENTS
Standing rules
These hold for the whole run, including after a compaction. Everything below this block is procedure; these are the bounds. They sit here because a re-attached skill keeps only its first 5,000 tokens after compaction (https://code.claude.com/docs/en/skills.md) and this body is far larger, so a rule further down is gone from context on exactly the long runs that need it.
Turn termination. Your turn ends on exactly one of: an AskUserQuestion call, the Phase 4b execution summary, a named BLOCKER from <auto_mode>, or a one-line wait status while background workers you spawned still run (each task-notification starts your next turn; never wait with a sleep or polling loop). Nothing else ends it. Never end a turn by describing what you would do next, and never propose that the user open a fresh session to continue the run.
Every branch that terminates the run deletes .ac/state/active-execution.json first. That is not bookkeeping. While the marker exists and no background worker is running, the plugin's Stop hook blocks the turn from ending and returns the outstanding step count to you (${CLAUDE_PLUGIN_ROOT}/hooks/stop-guard.sh); the marker's absence is what permits a terminal stop.
Context. Auto-compaction summarizes older turns and the run continues. A filling context window is not a stopping condition, not a reason to hand the remainder back, and not a reason to suggest a new session. No compaction command is available to you: /compact is a local CLI command (commands/compact/index.ts:5 sets type: 'local'; tools/SkillTool/SkillTool.ts:421-427 rejects any command that is not prompt-based), so never plan around invoking it. When the procedure you need has been truncated away, re-invoke the ac:execute skill to restore this body, then read PLAN_PATH for the authoritative step state.
What ships with it
7 files 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.
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.
- today Changed · +36 lines 5e74e111fec0
- 3d ago Changed · +37 lines e8bca07e61bc
- 5d ago Changed 2a7d597b7cda
- 18d ago Changed 3ea5d92febd3
- 22d ago Changed · +8 lines · -12 tokens per session scan B → A 5eabfb052044
- 1mo ago Changed · +197 lines · -158 tokens per session scan A → B 4e4aa8c02421
- 1mo ago First seen · 521 lines · 196 tokens per session scan A 240606380199
execute is a skill published in the GitHub repository anilcancakir/claude-code (3 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 15,061 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
vigil-instrument
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
monday-planning
Suggest a weekly training structure from recent load and deliver the plan.
pave-env
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.