Borrowing it
Nothing to install: this file belongs to rios0rios0/guide. 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/rios0rios0/guide/main/.github/workflows/generate-ai-rules/commands/fix-guardrails.mdgit clone --depth 1 https://github.com/rios0rios0/guideWrote 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/rios0rios0/guide/fix-guardrails)<a href="https://agentmods.dev/commands/rios0rios0/guide/fix-guardrails"><img src="https://agentmods.dev/badge/commands/rios0rios0/guide/fix-guardrails.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.00000 | $0.03489 |
| Opus 5 | $0.00000 | $0.01744 |
| Sonnet 5 | $0.00000 | $0.00698 |
| Haiku 4.5 | $0.00000 | $0.00349 |
Grade A, and why
fix-guardrails 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 6d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix all guardrail findings (make lint, make test, make sast) across one or more repositories. This command is a complete, repeatable workflow: sync with main, run all guardrails, fix every finding, update documentation, commit following standards, push, and create PRs.
For guardrail tools, refer to the CI/CD rule and Security rule. For commit conventions, refer to the Git Flow rule. For changelog updates, refer to the Documentation rule.
Arguments
$ARGUMENTS-- space-separated list of repository paths (absolute or relative to the current working directory). If empty, operate on the current working directory as a single repository.
Vendor Detection
Auto-detect the Git hosting vendor from git remote get-url origin to determine the correct PR creation CLI:
| Remote URL contains | Vendor | PR CLI |
|---|---|---|
github.com |
GitHub | gh pr create |
dev.azure.com or ssh.dev.azure.com |
Azure DevOps | az repos pr create |
gitlab.com or gitlab |
GitLab | glab mr create |
| Other | Unknown | Skip PR, report branch for manual creation |
Step-by-step Workflow (repeat for every repository)
Step 1 -- Sync with the default branch
cd <REPO_PATH>
git checkout <default-branch>
git fetch --all
git pull --rebase
- Detect the default branch with
git symbolic-ref refs/remotes/origin/HEAD(striprefs/remotes/origin/). Fall back tomainif unavailable. - If
pull --rebasefails due to conflicts, report the failure and skip this repo.
Step 2 -- Run all three guardrails
Run them in this exact order. Each gate must be evaluated independently -- even if one passes, the others may fail.
Gate 1: Lint
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.
- 6d ago First seen · 352 lines · 0 tokens per session scan A f7c2dd4a7a9d
fix-guardrails is a command published in the GitHub repository rios0rios0/guide (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,489 tokens. 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
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
zephyr-coverage-analysis
Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.
tdd
Test-driven change — write the failing test first, then implement.
impact
Blast radius of a change — impacted callers, tests, and contracts.