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 darrylmorley/ollama-plugin-cc/plugin install ollamaWrote 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/commands/darrylmorley/ollama-plugin-cc/execute-plan)<a href="https://agentmods.dev/commands/darrylmorley/ollama-plugin-cc/execute-plan"><img src="https://agentmods.dev/badge/commands/darrylmorley/ollama-plugin-cc/execute-plan/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/commands/darrylmorley/ollama-plugin-cc/execute-plan"><img src="https://agentmods.dev/badge/commands/darrylmorley/ollama-plugin-cc/execute-plan.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.00018 | $0.00352 |
| Opus 5.5 | $0.00007 | $0.00141 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
execute-plan 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 1mo 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.
What it actually says
Run the implement → verify → retry loop autonomously per step in the plan. The inner loop never crosses Claude's context.
Forward to the companion:
node "${CLAUDE_PLUGIN_ROOT}/scripts/ollama-companion.mjs" execute-plan $ARGUMENTS
Per step the pipeline:
- Implements via the agentic toolset (
read_file,write_file,apply_patch,run_command,done). - Captures the diff.
- Verifies each
successCriterionagainst the diff and the current state of in-scope files. - On pass, commits to git as
[ollama-plan <id>] step N: <description>and advances. - On fail, rolls back the working tree and retries with the verifier's feedback. Capped at
--max-retries(default 3).
If a step exhausts retries, the plan is marked stuck and execution returns to Claude. Use /ollama:replan <id> to refine, then /ollama:execute-plan <id> --resume-from <N> to continue.
Per-role model defaults: OLLAMA_PLUGIN_IMPLEMENTER_MODEL, OLLAMA_PLUGIN_VERIFIER_MODEL. CLI flags override env.
The pipeline refuses to start on a dirty working tree — commit or stash first.
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.
- 1mo ago First seen · 27 lines · 18 tokens per session scan A 1e4f56b5c5e1
execute-plan is a command published in the GitHub repository darrylmorley/ollama-plugin-cc (6 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 352 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.