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/madarauchiha-314/the-loop/create-ticketgit clone --depth 1 https://github.com/MadaraUchiha-314/the-loopWrote 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/madarauchiha-314/the-loop/create-ticket)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/create-ticket"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/create-ticket.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.00032 | $0.00518 |
| Opus 5 | $0.00016 | $0.00259 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
create-ticket 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
the-loop: create-ticket $ARGUMENTS
Turn an already-drafted requirements.md into a tracked work item. RULE: everything the
harness works on must have a ticket — this command creates it and wires the spec to it.
Read the the-loop skill, reference/collaboration.md and reference/workflow.md.
Load .the-loop/harness-config.yaml for ticketing (github | jira).
Steps
-
Read the requirements at
$ARGUMENTS. Use its introduction/user-stories to form the ticket title and body. -
Create the ticket in the configured ticketing system using the available integration (GitHub via
gh/GitHub MCP, or Jira via MCP):- Title from the requirement's summary; body links to the spec (do not paste the whole file — reference it, single source of truth).
- Apply the initial phase label
<workflow.phaseLabelPrefix>requirements-definition(labels are created by/the-loop:init).
-
Promote the folder. Derive the canonical id from the new ticket (e.g.
issue-42,PROJ-42). If the requirements live underdocs/specs/draft-<slug>/, rename that folder todocs/specs/<id>/— this carries any siblingbrainstorm.md(the root artifact) along with it. Update the front-matter of every promoted file (brainstorm.mdincluded):workItem: <id>,statusas appropriate. -
Reference on the ticket. Post/confirm a comment or description link pointing to the checked-in
docs/specs/<id>/requirements.md(single source of truth; later changes are edits to the file, not new comments). -
Report the ticket id/URL and the next step:
/the-loop:create-design <id>.
If the ticket already exists, do not duplicate it — reference it and just promote/link the spec.
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 · 42 lines · 32 tokens per session scan A 3df48d7887a7
create-ticket is a command published in the GitHub repository MadaraUchiha-314/the-loop (4 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 518 once invoked, about $0.0002 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
gaai-status
Show backlog, memory state & delivery readiness.
gaai-daemon
Launch or inspect the GAAI Delivery Daemon.
gaai-deliver
Launch or inspect the GAAI Delivery Daemon.
help
Show help for Ralph Specum plugin commands and workflow.
new
Create new spec and start research phase.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.