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/dsswift/ion/create-prgit clone --depth 1 https://github.com/dsswift/ionWhat 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.00025 | $0.02529 |
| Opus 5 | $0.00013 | $0.01264 |
| Sonnet 5 | $0.00005 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
create-pr 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the /create-pr command. Your job is to push the current feature branch and open a pull request into main with a well-structured description. The PR title and body are derived from the branch's commits and the issues they reference.
Hard rules.
- Never run on
main. Abort if the current branch ismain. - Only run
git pushas part of this command. No othergit pushoutside this flow. - Never merge to
main. The PR is opened — the user merges. - Do not create a PR with failing CI. If CI is already known to be failing, stop and report. Run the Linux parity gate (Step 3) before pushing so a Linux-only failure is caught locally — not after burning paid Actions minutes on a red PR.
- Zero tolerance for identifiable failures — pre-existing included. Every test failure, lint error, or build break that the parity gate (or any other check run during this command) surfaces MUST be fixed before the PR is opened. "Pre-existing on main", "not caused by this branch", and "unrelated to these changes" are forbidden dispositions — if the failure is visible before the PR exists, it blocks the PR. The full CI suite (
quality.yml: engine race + integration, desktop typecheck + tests, relay, iOS, lints) must be expected green, and any locally reproducible failure in that set is in scope to fix now, regardless of age or origin.
Step 1: Validate the branch
Run:
git branch --show-current
If the result is main, stop:
You're on
main. Switch to a feature branch before creating a PR.
Step 2: Check for uncommitted work
Run:
git status --porcelain
If there are uncommitted changes, stop:
There are uncommitted changes on this branch. Commit them before opening a PR.
Step 3: Linux parity gate (catch Linux-only CI failures before pushing)
CI runs engine-test (go test -race ./...) and desktop-test (npm test) on ubuntu-latest. Local development is on macOS, so OS-sensitive failures — path semantics, file-watcher timing, locale, goroutine starvation under the Linux race detector, eager require('electron') under npm ci --ignore-scripts — pass locally and only fail in CI. This step runs the same commands CI runs, in Linux containers, so those failures surface here instead of on the PR.
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 · 235 lines · 25 tokens per session scan A 6b4746817c20
create-pr is a command published in the GitHub repository dsswift/ion (4 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,529 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
memory-self-review
Mine recent agent history (claude-mem + usage stats) for recurring failures and repeated patterns, audit MEMORY.md health, and PROPOSE (never apply) CLAUDE.md/memory edits for human approval.
code-review
Provide a code review for the given pull request.
echo
This is a placeholder command definition for plugin framework tests.
dashclaw-quality
Recurring find-and-fix quality pass over the whole DashClaw app — browser smoke (frontend-verify) + code gates → triage → parallel worktree fixes → verify → ship. The goal prompt that drives the dashclaw-find-and-fix workflow.
dashclaw-retire-legacy
Officially retire the published dashclaw/legacy Node SDK the safe way — deprecate now, delete at v5 — without breaking external npm consumers. Drives the legacy-sdk-deprecation-sweep workflow.
apply-self-review
Apply the approved improvements from the latest memory-self-review PROPOSAL. Auto-applies the safe, reversible doc/memory edits (with backups); queues code/config/rule-rewrite edits for an explicit go. Never commits or pushes.