Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .claude/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .agents/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .cursor/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .gemini/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .github/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "gate-attribution" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/gate-attribution into .opencode/skills/gate-attribution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gate-attribution", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
gate-attribution
GitHub stars
494
Token cost
~749 tokens
SKILL.md length
312 words
Files
1
Skills in repo
91
Repo updated
First seen
Licence
MIT
At a glance
Per-task gate dispatch protocol for reviewer/testengineer set-dispatch attribution.
Works in 5 steps: For unrelated or high-risk tasks:… → For a true set-dispatch: Require one… → Minimize overhead via parallel dispatch… → …
SKILL.md covers The rule, Protocol, Optimization for trivial tasks and Why this exists
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Gate Attribution is an agent skill from ZaxbyHub/opencode-swarm. Per-task gate dispatch protocol for reviewer/testengineer set-dispatch attribution. Activates when dispatchlanes returns set-dispatch verdict rows that must be attributed to plan tasks. Documents single-task attribution plus parseable set-dispatch reviewer/testengineer rows.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
Example prompts
“/gate-attribution”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
1For unrelated or high-risk tasks: Dispatch separate reviewer and/or test_engineer lanes with exactly ONE taskId.
2For a true set-dispatch: Require one [REVIEWED] | task-id | verdict | ... (or [TESTED] | ...) row per task in the returned output. Each…
3Minimize overhead via parallel dispatch when set-dispatch is not appropriate
4Collect + attribute: Single-task lanes auto-attribute to their taskId; set-dispatch rows auto-attribute per parsed row.
5Do NOT rely on prose summaries: A batched dispatch without parseable rows is ambiguous and does not count per-task.
What it can do on your machine
Read from SKILL.md and the folder at commit b63a4bd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gate Attribution loads about 749 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 312 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~74
When it runs· the whole SKILL.md, loaded when a task matches
~749
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/gate-attribution/SKILL.md (or your agent's skills folder).
name
gate-attribution
description
Per-task gate dispatch protocol for reviewer/test_engineer set-dispatch attribution. Activates when dispatch_lanes returns set-dispatch verdict rows that must be attributed to plan tasks. Documents single-task attribution plus parseable set-dispatch reviewer/test_engineer rows.
audience
swarm-plugin
Gate Attribution
The rule
The gate tracker attributes reviewer/test_engineer dispatches PER TASK. A
single-task prompt still attributes by task_id / taskId / unambiguous prompt
task ID. A set-dispatch can also count per-task when the reviewer/test_engineer
output includes parseable per-task rows:
[REVIEWED] verdicts are APPROVED | REJECTED | CONCERNS; [TESTED] verdicts
are PASS | FAIL | SKIPPED. Rows with task-X.Y are normalized to X.Y;
unsafe or non-plan IDs are ignored.
Each parseable per-task verdict row creates gate evidence (regardless of verdict
value); the gate's pass/fail decision is made elsewhere from the accumulated
evidence. If no rows are parseable, attribution falls back to the single-task
rule.
Protocol
For unrelated or high-risk tasks: Dispatch separate reviewer and/or test_engineer lanes with exactly ONE taskId.
For a true set-dispatch: Require one [REVIEWED] | task-id | verdict | ... (or [TESTED] | ...) row per task in the returned output. Each parseable row creates gate evidence; the gate decision is made from the accumulated evidence.
Minimize overhead via parallel dispatch when set-dispatch is not appropriate:
dispatch_lanes_async with:
- common_prompt: shared verification context
- lanes: one lane per task, each with a single taskId
- max_concurrent: up to 3
This protocol applies only in sessions whose actual tool list includes the
swarm controller's dispatch tools; on hosts without the controller it is not
applicable — do not fabricate set-dispatch rows.
Collect + attribute: Single-task lanes auto-attribute to their taskId; set-dispatch rows auto-attribute per parsed row.
Do NOT rely on prose summaries: A batched dispatch without parseable rows is ambiguous and does not count per-task.
Gate evidence is persisted independently as .swarm/evidence/{taskId}.json for each task. Each parseable set-dispatch row causes the hook to write one task-scoped evidence file for that task (regardless of verdict value); a single multi-task evidence file cannot satisfy any task.
Optimization for trivial tasks
For pure ceremony gates (1-line doc fix):
TASK: Verify task X.Y. Run skill-mirrors.test.ts. PASS/FAIL.
taskId: X.Y
Why this exists
The gate tracker (the delegation-gate runtime) keys delegation chains by
sessionID. Ambiguous multi-task prompts still fail closed, but parseable
[REVIEWED] | task-id | ... rows provide explicit per-task attribution for
set-dispatches. Tracked in issue #1746 item 6.
Gate Attribution next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Gate Attribution compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Gate Attribution this skillZaxbyHub/opencode-swarm
Reviews a diff only for unnecessary complexity and lists what to delete or shrink, one numbered line per finding with the location, the cut and its replacement.
Runs a staged pull request or diff review using selected reviewer personas, checking the change against its stated intent and project standards before producing findings.
Quality-gate review of a reverse-engineering or assessment case package: scope readiness, Evidence-to-Finding-to-Path traceability, work-item coverage, timeline consistency, and artifact hashes.
Compares before and after Trailmark graphs of a branch, pull request or release diff to flag new entry points, tainted paths, removed validation and other structural security regressions.
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Monitor a pull request after creation and act autonomously on pushed PR activity.
496 GitHub stars~2.2k tokensUpdated today
Auto-check passed
Questions about Gate Attribution
What does Gate Attribution do?
Per-task gate dispatch protocol for reviewer/testengineer set-dispatch attribution. Gate Attribution is an agent skill from ZaxbyHub/opencode-swarm. Per-task gate dispatch protocol for reviewer/testengineer set-dispatch attribution.
How do I install Gate Attribution in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a claude-code`. Or copy the skill folder (.opencode/skills/gate-attribution in ZaxbyHub/opencode-swarm) into .claude/skills/gate-attribution in your project. Claude Code loads it when a task matches its description.
How do I install Gate Attribution in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a codex`. Or copy the skill folder (.opencode/skills/gate-attribution in ZaxbyHub/opencode-swarm) into .agents/skills/gate-attribution in your project. Codex loads it when a task matches its description.
Can I use Gate Attribution in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZaxbyHub/opencode-swarm --skill gate-attribution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gate-attribution, .gemini/skills/gate-attribution, .github/skills/gate-attribution and .opencode/skills/gate-attribution in your project.
What does Gate Attribution need to run?
SKILL.md names no scripts, command-line tools or credentials: Gate Attribution is instructions for the agent only.
Does Gate Attribution access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gate Attribution safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gate Attribution use?
Gate Attribution is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gate Attribution use?
About 749 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gate Attribution?
Skills that share tags, products or a category with Gate Attribution: Over-Engineering Review (DietrichGebert/ponytail, 160k stars), AI Prompt Engineering Safety Review (github/awesome-copilot, 40k stars), Compound Engineering Code Review (EveryInc/compound-engineering-plugin, 25k stars) and Case Review (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gate Attribution?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 494 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 10, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
