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/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/fix-status)<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/fix-status"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/fix-status.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.1 | $0.00013 | $0.00645 |
| Opus 5 | $0.00006 | $0.00322 |
| Sonnet 5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
fix-status 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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Status: Review Active Fix Branches
List all active fix branches created by /sentry:fix-error, show their status, and manage them (merge or discard).
Workflow
-
List worktrees: Run
git worktree listand parse the output. -
Filter fix branches: Keep only worktrees whose branch name matches
fix/SENTRY-*. -
For each fix worktree, gather:
- Branch name: from the worktree list output
- Worktree path: the filesystem path
- Latest commit: Run
git -C {worktree_path} log -1 --onelineto get the last commit message - Files changed: Run
git -C {worktree_path} diff --stat HEAD~1 HEAD 2>/dev/null(if a commit exists) - Status: Determine based on:
- If a commit with
fix:prefix exists → "Complete" - If no new commits beyond the branch point → "In progress" (agent may still be working)
- If a commit with
-
Present results as a markdown table:
## Active Fix Branches | Branch | Status | Last Commit | Files Changed | Actions | |--------|--------|-------------|---------------|---------| | fix/SENTRY-PROJECT-123-nil-check | Complete | fix: TypeError (Sentry PROJECT-123) | 2 files | merge / discard | | fix/SENTRY-PROJECT-124-timeout | In progress | — | — | wait | -
Handle developer actions: If the developer asks to merge or discard:
Merge:
-
Run
git merge {branch_name}from the main working tree -
If merge succeeds: run
git worktree remove {worktree_path} -
If merge conflicts: report the conflicts and let the developer resolve manually
-
Suggest resolving the Sentry issue:
Fix merged. Resolve this issue in Sentry? Use: /sentry:resolve {issue_id}Extract the issue ID from the branch name (
fix/SENTRY-{short_id}-*).
Discard:
- Run
git worktree remove {worktree_path} --force - Run
git branch -D {branch_name} - Confirm: "Worktree and branch
{branch_name}have been removed."
-
-
If no fix worktrees exist: Report "No active fix branches found. Use
/sentry:fix-errorto launch a fix."
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.
- 5d ago First seen · 62 lines · 13 tokens per session scan A 8e543d0392b0
fix-status is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (661 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 645 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
payload-revert
Stage reverts for high-confidence payload candidates identified by payload-analysis.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
fix-issue
Analyze and fix the GitHub issue: $ARGUMENTS.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…