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.
git clone --depth 1 https://github.com/dsswift/ionWrote 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/dsswift/ion/create-issue)<a href="https://agentmods.dev/commands/dsswift/ion/create-issue"><img src="https://agentmods.dev/badge/commands/dsswift/ion/create-issue/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/dsswift/ion/create-issue"><img src="https://agentmods.dev/badge/commands/dsswift/ion/create-issue.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.00028 | $0.03318 |
| Opus 5.5 | $0.00011 | $0.01327 |
| Sonnet 5.5 | $0.00006 | $0.00664 |
| Haiku 4.5 | $0.00003 | $0.00332 |
Grade A, and why
create-issue 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 16d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-issue
Open a GitHub issue on dsswift/ion from the current conversation. The issue gives Ion developers enough to know what to build and how it should behave, and it carries nothing about the consumer project that surfaced the need.
Rules
- The issue is created on
dsswift/ion. - The issue names no consumer project. That covers project, product, company, team, and person names, internal paths, domain terminology, and proprietary APIs. This is a confidentiality boundary.
- The issue is written in Ion vocabulary (
docs/vocabulary/terms.json): hooks, events, tools, SDK types, config fields, providers, protocol commands, sessions, extensions, harnesses, Environments, the Studio wire, Studio SDK resources. A consumer concept with no Ion term is described as a capability gap: "a consumer needs to…", "an extension wants to…". - The operator reviews the draft before the issue is created. The operator is the final confidentiality gate.
- Every GitHub operation goes through
gh, which is already authenticated. - The command ends when the issue is created and the report is printed.
Arguments
$ARGUMENTS is optional. It adds context, focus, or a classification hint.
/create-issuederives everything from the conversation./create-issue bug: error events are not emitted when tool execution failsgives a classification and a focus./create-issue we need a hook that fires before compactiongives a feature focus.
A classification keyword (bug, feature, enhancement) in $ARGUMENTS decides Step 2.
Step 1: Extract the need
From the conversation, extract:
- What is missing or broken. The specific behavior, hook, event, config field, protocol command, SDK method, wire action, or tool capability.
- Why it matters. What a consumer or extension cannot do today. Name the class of consumer that benefits.
- What the capability looks like. The contract on Ion's public surface: the hook fires at X, the event carries Y, the config field controls Z.
- What was tried. The Ion primitives that were reached for and why they fell short.
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.
- 16d ago Changed · -41 lines · -1 tokens per session a9ce976f3f9b
- 1mo ago Changed · -1 lines fbeba80f4094
- 1mo ago 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 28 tokens to every session and 3,318 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
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
create-task-list-for-issue.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
update-smart.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
github-swarm
Create a specialized swarm for GitHub repository management.
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.