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 skills/breezewish/codexpotter/loopnpx skills add breezewish/CodexPotter --skill loopgit clone --depth 1 https://github.com/breezewish/CodexPotterWhat 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.00011 | $0.02683 |
| Opus 5 | $0.00005 | $0.01341 |
| Sonnet 5 | $0.00002 | $0.00537 |
| Haiku 4.5 | $0.00001 | $0.00268 |
Grade A, and why
loop 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodexPotter Loop
This is a control protocol for running subagents in a loop pattern to "reconcile" repo to fulfill the objective provided by the user, which may be a complex task or target state.
Subagents own all task execution. You only coordinate the loop.
| Marker | Meaning | Your action |
|---|---|---|
| none | Work is not proven complete | Continue with the same subagent |
::potter(ready) |
Candidate completion; needs fresh-context verification | Close the subagent and start a fresh one next round |
::potter(exit) |
Fresh-context verification passed | Stop with state complete |
Control parameter:
rounds=N(default10): maximum counted rounds
Your rules:
- Do only the control actions this skill explicitly requires.
- Do NOT implement, review, fix, test, or inspect repository.
- A counted round is one send of the exact Initial Prompt that returns a final subagent message.
- Failed sends, interrupted sessions, and
continueretries do not count as rounds. - Reach Limit Prompt does not count as a round.
- Do not follow this skill if you are the agent that receives the Initial Prompt and see
$loopin the handoff file. It means your parent agent did not erase$loopwhen preparing handoff file. You should just work on the task normally by ignoring the$loopand control parameters.
1. Handoff
If the user provides an existing CodexPotter handoff file path (it must conform to the path below), reuse it.
Otherwise create a new handoff file:
.codexpotter/projects_v3/{yyyy}_{mm}_{dd}_{slug}.md
where:
{slug}is a short descriptive name generated from the user request, like "add_login_feature".
Use a path relative to the current repo/worktree root. Do not overwrite an existing file.
For a new file, write:
# Objective
## Original User Request
<The user's exact original message text, keep text unchanged, except remove `$loop` and
control parameters such as `rounds=N`>
## Important Context, Constraints, and User Preferences
<Concise factual context from previous turns to make this handoff self-contained>
## Critical Data, Examples, and References
<Concise factual data from previous turns to make this handoff self-contained>
# Done
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.
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.
- 2d ago First seen · 271 lines · 11 tokens per session scan A 1af78502ebef
loop is a skill published in the GitHub repository breezewish/CodexPotter (630 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,683 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-30.
Other skills, from other repositories
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
greeting-user
Explains how to properly greet the user.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
canvas
Display HTML content on connected OpenClaw nodes (Mac app, iOS, Android).
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…