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 it235/multica-best-practices --skill multica-gate-setupgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/multica-gate-setup)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-gate-setup"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-gate-setup.svg" alt="Measured on agentmods" 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.00049 | $0.01360 |
| Opus 5 | $0.00024 | $0.00680 |
| Sonnet 5 | $0.00010 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
multica-gate-setup 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate Setup (CI gate integration)
What this is
An integration Skill that upgrades "verification" from agent self-discipline to machine-executed CI.
Core idea (multica-gatekit): the gate issuer must be a different party from the gated — authors can't stamp "tests passed" on themselves; only CI's actual run results count.
This Skill answers two questions:
- How do you install gates into a repository? (one-time deployment)
- How does gatekeeping read the CI verdict? (G2 on every task)
Template files it carries
The 3 template files needed for deployment live in the same directory as this SKILL.md (the Skill is self-contained; copy them together with the skill):
| File | Purpose |
|---|---|
delivery-gate.yml |
CI workflow: runs lint + test + build on PRs and writes a structured gate conclusion |
branch-protection.json |
Branch protection rules: require the delivery-gate status check to pass + independent approval before merging |
apply-branch-protection.sh |
Applies the protection rules to the repo with the gh CLI (edit the placeholders, then run) |
Fit: you already have runnable test / lint / build commands; you don't want "Worker self-certifies done" to leave room for cheating; multiple squads in parallel need a unified merge gate.
Capability prerequisites (route by environment)
The Leader only has the Skill + MCP, no shell. So branch by the runtime environment:
| Capability | Gatekeeping (G2) | Deployment (one-time) |
|---|---|---|
| Has GitHub MCP (read) | Real integration: query check-runs to read the CI verdict | — |
| Has GitHub MCP (write) | — | Real integration: create the workflow + set branch protection |
| No MCP | Weak integration: read the CI verdict humans paste into the PR comment | Human runs the script; you verify the output |
Deployment flow (one-time)
- Read the 3 template files in this Skill's directory:
delivery-gate.yml/branch-protection.json/apply-branch-protection.sh. - Replace the placeholders for the target repository:
What ships with it
3 files 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.
- 7d ago First seen · 91 lines · 49 tokens per session scan A 6fa6823b41bf
multica-gate-setup is a skill published in the GitHub repository it235/multica-best-practices (104 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,360 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-30.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.