Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.claude/commands/fix-tickets.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/alfredoperez/speckit-companion/fix-tickets)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/fix-tickets"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/fix-tickets/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/alfredoperez/speckit-companion/fix-tickets"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/fix-tickets.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.00049 | $0.06987 |
| Opus 5 | $0.00024 | $0.03494 |
| Sonnet 5 | $0.00010 | $0.01397 |
| Haiku 4.5 | $0.00005 | $0.00699 |
Grade A, and why
fix-tickets 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 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.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this does
A self-hosting build loop for speckit-companion. For each ticket, in strict sequence:
Two modes. The default (below) is the full loop: one issue per ticket, fixed by driving the SpecKit Companion pipeline on itself.
--light(Light mode) drops the issue, the spec pipeline, and the sequencing for small mechanical changes, and fans out parallel worktree agents instead. It keeps the code review, tests, and CI. Light mode trades away the dogfooding signal — pick it deliberately, not by default.
- Clean slate + install-local FIRST — on
main,git fetch && git pull --ff-only, then run/install-localso this ticket is fixed by the freshest build and the latest/speckit.companion.*commands (the previous ticket's merge lands here). Discard the throwaway version bump, assert a clean tree. Refuse to start dirty. - Fix — drive the SpecKit Companion pipeline to fix the ticket.
- Code review — run
/code-review, apply findings; re-run it on any fix that itself changed real logic. - PR — open a PR with
/create-prconventions. - Merge — squash-merge, delete branch.
- Capture learnings + tick the box — distill this ticket's review findings and route each to where it fires (review check →
.claude/review-checklist.md; authoring convention → a proposedCLAUDE.mdedit; loop mechanics → this file; gap → an issue candidate), so the next ticket's fix avoids the same bug class. Then check the ticket off in the vault'sCurrent.mdqueue with its PR link. - Next ticket — its step 1
/install-localinstalls this ticket's merge. After the last ticket, a closing/install-localinstalls the final merge. This is the point of the loop: prove the companion keeps working on itself as it improves.
After all tickets: write one run report (markdown, via the vault obsidian skill, into Projects/speckit companion/reports/) of everything fixed, in plain language, flagging UI / manual-test items so you know exactly what to verify by hand, what was already exercised by the pipeline (don't re-test), the new lessons captured, and any architecture/skill flags worth promoting. Use /html-page only to export it if it needs to leave the vault — HTML in the vault is unsearchable.
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 Changed · +6 lines 4290d1d92372
- 11d ago First seen · 259 lines · 49 tokens per session scan A b493e9e49ed7
fix-tickets is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 6,987 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-30.
Other commands, from other repositories
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
pr-package
Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…
open-pr
Create a pull request for the current branch following the the team's standard PR template.
generate-linear-worklog
You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.
add-changelog
Generate and maintain project changelog.
git-status
Command "git-status" from qdhenry/Claude-Command-Suite, covering git status command and instructions.