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 skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitorgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/skills/zaxbyhub/opencode-swarm/ci-fix-monitor)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/ci-fix-monitor"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/ci-fix-monitor/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/skills/zaxbyhub/opencode-swarm/ci-fix-monitor"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/ci-fix-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 22 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 14 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 15 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00068 | $0.00539 |
| Opus 5.5 | $0.00027 | $0.00216 |
| Sonnet 5.5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
ci-fix-monitor 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 14d 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
CI Fix Monitor
Read .opencode/skills/ci-fix-monitor/SKILL.md for the full protocol.
Also load:
.agents/skills/commit-pr/SKILL.mdbefore committing or pushing any fix.agents/skills/engineering-conventions/SKILL.mdif the fix touches source files.agents/skills/running-tests/SKILL.mdbefore running any test suite as part of a fix
Codex-specific execution notes:
- MCP tool names (
mcp__github__*) are injected by the runtime harness and may differ across environments. Verify availability viaToolSearchbefore first use in a session. - No
ghCLI available. Usemcp__github__pull_request_read(methodget_check_runs) to list check status andmcp__github__get_job_logs(withreturn_content: true) to fetch failure logs. - For
package-checkfailures:package-checkvalidates the npm tarball (npm pack+ tarball contents). A failure is a source/build/package-manifest problem, not generated-file drift.dist/is generated and NOT committed — do not stage it; runbun run buildlocally only when you need the bundle to verify (e.g.node --input-type=module -e "await import('./dist/index.js'); console.log('dist import OK')"). There is no longer a committed-dist drift check. - For a branch behind main (version-drift):
git fetch origin main && git rebase origin/main(abort withgit rebase --abortif conflicts occur and escalate to user), thengit push --force-with-lease origin <branch>. Force-push is required and expected after rebase. - For format violations:
bunx biome format --write <specific-file>— do NOT runbiome format --write .on the whole repo. - After any source fix, run the focused test file (
bun test <file>) before committing. - Do not declare victory until ALL required checks show green;
skippedis acceptable only if the same check was skipped on the base branch.
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.
- 14d ago Changed · +1 lines f0fdc0200212
- 1mo ago First seen · 26 lines · 68 tokens per session scan A f48f554bb9b8
ci-fix-monitor is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (513 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 539 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.