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 swarm-ci-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/swarm-ci-monitor)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/swarm-ci-monitor"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/swarm-ci-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/swarm-ci-monitor"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/swarm-ci-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- 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 31 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.00075 | $0.00507 |
| Opus 5 | $0.00037 | $0.00253 |
| Sonnet 5 | $0.00015 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
swarm-ci-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 13d 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
Swarm CI Monitor
Read and follow ../../../.opencode/skills/swarm-ci-monitor/SKILL.md as the
canonical workflow.
Codex 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 in the remote/MCP environment. Use MCP tools instead:- PR checks →
mcp__github__pull_request_readmethodget_check_runs - Failure logs →
mcp__github__get_job_logswithjob_id,return_content: true - PR mergeable/mergeStateStatus/reviewDecision →
mcp__github__pull_request_readmethodget
- PR checks →
- Merge is new surface area. There is no
mcp__github__merge_pull_requestreference anywhere else in the repo. Verify availability viaToolSearchbefore first use in a session. If the tool is unavailable, do not attempt a fallback that contradicts the "noghCLI" premise above — surface to the user that the merge must be done manually. "ToolSearchdidn't confirm the tool but I'll try it anyway" is not acceptable for the one action in this skill that cannot be safely undone — surface to the user instead. - Do not soften Step 1's pre-flight gates or Step 3's pre-merge re-check — this is the first skill in the repo authorized to execute a merge.
- Load
../commit-pr/SKILL.mdbefore committing or pushing any fix, and../../../.opencode/skills/ci-fix-monitor/SKILL.mdfor failure-type-specific fix recipes, as the canonical's Composition section directs. - Do not declare victory until the post-merge local-git confirmation (Step 4b) passes. Green checks alone are not sufficient.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 36 lines · 75 tokens per session scan A 6ef7e1a6ea0f
swarm-ci-monitor is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 507 once invoked, about $0.0004 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-30.
Other skills, from other repositories
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
github-ci-fix
Use when PR checks fail, CI is red, or GitHub Actions workflows break - systematically inspects failing checks via gh CLI, pulls logs, checks for flakiness and scopes the breaking commit, scopes external checks, then creates fix plan using existing plan skill.
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.
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.
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…