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.
npx skills add naimkatiman/continuous-improvement --skill executegit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/execute)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/execute"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/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/naimkatiman/continuous-improvement/execute"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/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.00012 | $0.00388 |
| Opus 5 | $0.00006 | $0.00194 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
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.
This is a copy
100% identical to execute — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Execute
Use this skill when the work is understood and the job is to build it.
This is the canonical execution workflow. autopilot, ralph, ultragoal,
ultrapilot, pipeline, and swarm route here.
Goal
Take a task from agreed intent to working code, with evidence that it works.
Workflow
- Confirm the task is clear enough to build. If it is not, plan first.
- Break the work into independent units; run genuinely independent units in parallel.
- Implement the smallest correct change per unit, reusing existing utilities and patterns.
- Verify as you go, not only at the end.
- Report what changed, what was verified, and what remains.
Scale
Match the machinery to the task:
- Single unit — implement directly, verify, done.
- Several independent units — delegate to
executoragents in parallel. - Long-running or unbounded — keep a durable task list and continue until the list is empty.
- Needs coordinated parallel workers — use
team.
Do not spin up coordination for work that one focused pass would finish.
Rules
- Prefer deletion over addition when behavior is preserved.
- Do not add dependencies without an explicit request.
- Keep diffs small and reversible.
- Placeholder TODOs,
test.skip, and stub tests are blockers, not progress. - Authoring and approval are separate passes — do not self-approve; hand off to
revieworverify.
Completion
Before claiming done:
- No pending tasks
- Tests pass, or failures are reported plainly
- Verification evidence collected
Output
- Files changed
- What was implemented
- Evidence it works
- What is still open
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.
- yesterday First seen · 50 lines · 12 tokens per session scan A 7d7fdc3be106
execute is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 388 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to execute, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ap-policies
Attach a completion policy gate (shell check or judge-agent rubric) to a session or fan-in group so turn-end only passes when the gate is green, then optionally auto-commit pending human ack. Use when the user says "gate this session on tests passing", "attach a policy", "commit only if tests are green", "judge…
ml-verify
Use when the user wants to verify code, config, or math before running — or proactively before any expensive training job or deployment.
verify
Run real verification — tests, type checks, and linting.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
darwinian-evolver
Evolve prompts/regex/SQL/code with Imbue's evolution loop.
mantis-reproduce
Generates and runs crash reproducers to verify security flaws. Use when viable findings exist and you need to write and execute a script or payload to verify the crash. Don't use for code auditing or patching.