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 agentmods add commands/darrylmorley/ollama-plugin-cc/plangit clone --depth 1 https://github.com/darrylmorley/ollama-plugin-ccWrote 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/plan)<a href="https://agentmods.dev/commands/darrylmorley/ollama-plugin-cc/plan"><img src="https://agentmods.dev/badge/commands/darrylmorley/ollama-plugin-cc/plan.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00259 |
| Opus 5 | $0.00009 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
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 4d 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 plan subcommand of the Ollama companion. The planner uses a read-only agentic loop (read_file, list_directory) to ground itself in the actual codebase before emitting a structured JSON plan.
Forward the raw user request to the companion:
node "${CLAUDE_PLUGIN_ROOT}/scripts/ollama-companion.mjs" plan $ARGUMENTS
The output is rendered markdown showing the plan's task, rationale, confidence score, scope, and steps with success criteria. The final lines suggest follow-up commands (/ollama:execute-plan or /ollama:replan).
Review the plan before approving. If the rationale is shaky or the scope is wrong, refine with /ollama:replan <plan-id> "<your feedback>". If the plan looks correct, proceed with /ollama:execute-plan <plan-id>.
Per-role model defaults can be set via env: OLLAMA_PLUGIN_PLANNER_MODEL (falls back to OLLAMA_PLUGIN_DEFAULT_MODEL).
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.
- 4d ago First seen · 20 lines · 17 tokens per session scan A eb6ebb091c43
plan is a command published in the GitHub repository darrylmorley/ollama-plugin-cc (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 259 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.