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/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/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/madarauchiha-314/the-loop/create-ticket"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/create-ticket.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.00032 | $0.00680 |
| Opus 5.5 | $0.00013 | $0.00272 |
| Sonnet 5.5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 12d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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. The ticketing system is whatever the repository's
remote and the available integration are (GitHub via the-loop ticket create --repository, Jira via the-loop ticket create --project) — it is no longer a
harness-config key (issue-352).
Steps
-
Read the requirements at
$ARGUMENTS. Use its introduction/user-stories to form the ticket title and body. -
Create the ticket in the project's ticketing system (GitHub:
the-loop ticket create --repository OWNER/REPO --title … --body-file … --label loop:requirements-definition, which needs nogh— issue-447;ghonly when the CLI is not installed. Jira:the-loop ticket create --project KEY …with the same flags, in a project listed underintegrations.jira.projects; it prints the newjira:SITE/KEY-Nref and writes labels in their Jira-safe form. The Jira MCP tools only when the CLI is not installed):- 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
loop:requirements-definition(labels are created by/the-loop:init).
-
Promote the folder. Derive the canonical id from the new ticket (e.g.
issue-42, orjira-proj-42forjira:SITE/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 (
the-loop comment) or confirm a comment or description link pointing to the checked-indocs/specs/<id>/requirements.md(single source of truth; later changes are edits to the file, not new comments).
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.
- 12d ago Changed · +4 lines f217dc400b63
- 18d ago Changed · +2 lines 9ad9860d624f
- 1mo ago Changed · +2 lines f14f1856b27b
- 1mo 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 (7 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 680 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
close
They operate it without you.
okr
Create or review OKRs (Objectives and Key Results).
project-health
Assess overall project health across code quality, tests, docs, and activity.
retro
Run a sprint retrospective with data-driven insights from git history.
sprint-health
Check current sprint health and identify risks.
sprint-plan
Plan a sprint by analyzing backlog, estimating capacity, and selecting work.