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-issuegit 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.00029 | $0.04800 |
| Opus 5 | $0.00015 | $0.02400 |
| Sonnet 5 | $0.00006 | $0.00960 |
| Haiku 4.5 | $0.00003 | $0.00480 |
Grade A, and why
create-issue scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Use the GitHub CLI (`gh`) for all GitHub operations.** Do not use `WebFetch`, `curl`, or any direct HTTP calls to the GitHub API. The `gh` CLI is already authenticated; raw API calls are not. How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a GitHub issue on the dsswift/ion repository based on the current conversation. The issue must contain enough context for Ion engine developers to understand what to implement and how it should behave — without leaking any details about the consumer project that surfaced the need.
Hard rules. These are load-bearing.
- The issue is created on
dsswift/ion. Never create on any other repo. - The issue must contain zero references to the consumer project. No project names, product names, company names, internal paths, domain-specific terminology, proprietary APIs, team names, or person names from the consumer side. This is a confidentiality boundary, not a style preference.
- The issue must be written entirely in Ion engine vocabulary: hooks, events, tools, SDK types, config fields, providers, protocol commands, normalized events, engine sessions, extensions, harnesses, consumers. If a concept from the consumer project doesn't map to Ion vocabulary, describe the capability gap in generic terms ("a consumer needs to…", "an extension wants to…", "a harness using the SDK expects to…").
- You must present the draft to the user for review before creating the issue. The user is the final confidentiality gate.
- Use the GitHub CLI (
gh) for all GitHub operations. Do not useWebFetch,curl, or any direct HTTP calls to the GitHub API. TheghCLI is already authenticated; raw API calls are not. - After the issue is created, stop. Do not start implementing.
Arguments
$ARGUMENTS — optional. When present, provides additional context, focus, or classification hints. Examples:
/ion--open-issue— derive everything from the conversation/ion--open-issue bug: error events are not emitted when tool execution fails— explicit classification + focus/ion--open-issue we need a hook that fires before compaction— feature focus
If $ARGUMENTS contains an explicit classification keyword (bug, feature, enhancement), use it as a strong signal in Step 2. Otherwise, auto-detect.
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 · 397 lines · 29 tokens per session scan A f8bbc6bd5288
create-issue is a command published in the GitHub repository dsswift/ion (4 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 4,800 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.