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/developerz-ai/universal-lsp/fix-cigit clone --depth 1 https://github.com/developerz-ai/universal-lspWrote 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/developerz-ai/universal-lsp/fix-ci)<a href="https://agentmods.dev/commands/developerz-ai/universal-lsp/fix-ci"><img src="https://agentmods.dev/badge/commands/developerz-ai/universal-lsp/fix-ci.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 | $0.00017 | $0.00343 |
| Opus 5 | $0.00009 | $0.00171 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
fix-ci 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 2d 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
/fix-ci
-
gh run list --branch $(git branch --show-current) --limit 3 -
gh run view <id> --log-failed— read the actual error, not the summary. -
Map the job to its local command (they are the same strings; the mapping lives in
scripts/lib/gate.ts):Job Local Format + guards bin/check --files <paths>Build + test bin/dev testgraph-lite standalone cmake -S graph-lite -B build/graph-lite-standalone -G Ninja && cmake --build build/graph-lite-standaloneASan + UBSan bin/dev asanclang-tidy clang-tidy -p build/dev <file> -
Reproduce locally first. A fix pushed without reproducing is a guess with a five-minute feedback loop.
-
Fix,
bin/check --changed, push.
If the job failed because CI and the local gate disagree, that is the parity bug —
fix scripts/lib/gate.ts and .github/workflows/ci.yml together, and
bun test scripts/ proves it.
Flaky is not acceptable. A flaky job trains everyone to re-run instead of
read. Open an issue and quarantine it; never continue-on-error.
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.
- 2d ago First seen · 31 lines · 17 tokens per session scan A af8f2e9fcf41
fix-ci is a command published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 12d ago), licensed Apache-2.0. It adds 17 tokens to every session and 343 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-08-31.
Other commands, from other repositories
release
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
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.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
remediate
Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…