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/mbanderas/costguard/costguard-fixgit clone --depth 1 https://github.com/mbanderas/costguardWrote 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/mbanderas/costguard/costguard-fix)<a href="https://agentmods.dev/commands/mbanderas/costguard/costguard-fix"><img src="https://agentmods.dev/badge/commands/mbanderas/costguard/costguard-fix.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.00036 | $0.00509 |
| Opus 5 | $0.00018 | $0.00254 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
costguard-fix 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.
What it actually says
Apply Costguard's CI auto-fixes (or preview them).
Requested action: $ARGUMENTS
Costguard is a built CLI bundled with this plugin at
${CLAUDE_PLUGIN_ROOT}/dist/cli/index.js. It reads a workspaces.json
registry from the current working directory.
-
Run the fixer, passing the user's arguments straight through:
node "${CLAUDE_PLUGIN_ROOT}/dist/cli/index.js" fix $ARGUMENTS- Default is dry-run: with no
--apply, the CLI prints a unified-diff preview of every change and writes nothing. Show that preview to the user. --applywrites the surgical edits to the workspace's CI files on disk (only the deterministic ADD-rule fixers: timeout, concurrency, paths-ignore). It is idempotent — re-running applies nothing new.--pradditionally writes local PR artifacts (branch.txt,fix.patch,pr-body.md); it does not push or open anything by itself.- A name or
--allis required, else the CLI printsError: specify workspaces or --all.
- Default is dry-run: with no
-
Report the CLI's stdout verbatim (the diff preview, or the applied-rules summary). Relay any
Error:line on non-zero exit.
Notes:
- Prerequisite: the plugin runs the built
dist/. If${CLAUDE_PLUGIN_ROOT}/dist/cli/index.jsis missing, runpnpm buildonce from the costguard checkout. - Costguard never pushes git.
--open-pris gated and refuses without an explicit token; even then it only opens a PR, never force-pushes. For the normal flow, prefer--apply(or--prfor reviewable artifacts) and let the human commit. - Only auto-fixable findings (the in-repo CI files) are touched. Cloud/provider findings are advisory and never auto-fixed.
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 · 45 lines · 36 tokens per session scan A fb907ee2048e
costguard-fix is a command published in the GitHub repository mbanderas/costguard (2 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 509 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
sentinel
GitHub-aware work monitor - triages issues, PRs, and CI failures.
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.