Borrowing it
Nothing to install: this file belongs to rakaarwaky/qwen-web-arwaky. 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/rakaarwaky/qwen-web-arwaky/main/.agents/skills/setup-ci-quality-gates/SKILL.mdgit clone --depth 1 https://github.com/rakaarwaky/qwen-web-arwakyWrote 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/rakaarwaky/qwen-web-arwaky/setup-ci-quality-gates)<a href="https://agentmods.dev/skills/rakaarwaky/qwen-web-arwaky/setup-ci-quality-gates"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/setup-ci-quality-gates/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/rakaarwaky/qwen-web-arwaky/setup-ci-quality-gates"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/setup-ci-quality-gates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.02752 |
| Opus 5 | $0.00039 | $0.01376 |
| Sonnet 5 | $0.00016 | $0.00550 |
| Haiku 4.5 | $0.00008 | $0.00275 |
Grade A, and why
setup-ci-quality-gates scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `test` | `cargo nextest run --workspace --lib --tests -j 2` | needs: build; install nextest via curl | How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Quality Gates System
Replicate the CI setup used by this repo: quality gates enforced by GitHub Actions + a branch-protection ruleset, architecture enforcement via the project's own linter (self-lint), and four AI review layers (CodeRabbit, Codacy, cubic, Repowise). This is a copy-and-extend blueprint, not a one-off checklist — adapt names and paths to the target repo.
Language-agnostic. The pattern (quality gates → branch protection → AI review) applies to any language. The commands below are this repo's Rust flavor; substitute per language:
| Concern | Rust | Python | TypeScript/JS |
|---|---|---|---|
| Format | cargo fmt --check |
ruff format --check |
prettier --check |
| Lint | cargo clippy -D warnings |
ruff check + mypy |
eslint + tsc --noEmit |
| Tests | cargo nextest run |
pytest |
vitest / jest |
| Security deps | cargo audit |
bandit + pip-audit |
npm audit / eslint-plugin-security |
| Build | cargo build --release |
python -m build |
tsc / vite build |
The self-lint job is the one part that is inherently project-specific: it
runs this linter (lint-arwaky-cli) on the repo's own multi-language
workspace (crates/, modules/, packages/).
Architecture overview
PR opened / pushed
│
├─ CI workflow (.github/workflows/ci.yml)
│ ├─ Format (cargo fmt --check)
│ ├─ Clippy (cargo clippy -D warnings)
│ ├─ Build (cargo build --release)
│ ├─ Tests (cargo nextest run)
│ └─ Self-Lint (lint-arwaky-cli check . == 0 violations)
│
├─ Codacy Static Code Analysis (app.codacy.com)
├─ CodeRabbit (app.coderabbit.ai) — change review
├─ cubic AI reviewer (www.cubic.dev) — ultrareview
└─ Repowise bot (.repowise/bot.yaml) — health gate advisory
│
└─ Ruleset "Protect main" (GitHub rulesets)
├─ required_status_checks: Format, Clippy, Build, Tests,
│ Self-Lint, Codacy Static Code Analysis
├─ strict: true (must be up to date)
├─ non_fast_forward + deletion: blocked
└─ auto-merge workflow (squash) merges when all pass
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.
- 11d ago First seen · 265 lines · 79 tokens per session scan A f119e7f20095
setup-ci-quality-gates is a skill published in the GitHub repository rakaarwaky/qwen-web-arwaky (13 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 2,752 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
review
Review before merge. Stage-1 spec-compliance gate, then risk-selected Stage-2 review axes from the canonical set. analyst always runs, callers can pin extra always-on axes, and explicit deep review runs the full 16-axis set. Run after /test. Do NOT invoke code-qualities-assessment, doc-accuracy, golden-principles, or…