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 agentmods add skills/zaxbyhub/opencode-swarm/gate-attributionnpx skills add ZaxbyHub/opencode-swarm --skill gate-attributiongit 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/gate-attribution)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/gate-attribution"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/gate-attribution.svg" alt="Measured on agentmods" height="20"></a>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.00055 | $0.00714 |
| Opus 5 | $0.00028 | $0.00357 |
| Sonnet 5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
gate-attribution 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 today.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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] | task-2.1 | APPROVED | ...
[TESTED] | 2.1 | PASS | ...
[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:
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.dispatch_lanes_async with: - common_prompt: shared verification context - lanes: one lane per task, each with a single taskId - max_concurrent: up to 3 - 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.
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.
- today Changed · +3 lines 4f998687357a
- 6d ago First seen · 55 lines · 55 tokens per session scan A ef7894d8e437
gate-attribution is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (463 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 714 once invoked, about $0.0003 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
ux-create-manifest
Create the initial Product UX Bible for an existing web or full-screen web app by deeply auditing the repository, using sub-agents when available, and generating docs/ux manifests, schemas, budgets, surface maps, action taxonomy, and design-token policies from observed code.
ux-principal
Principal UX architect skill for deciding WHERE a UI feature belongs, before it is implemented. Reads and maintains docs/ux manifests, classifies the feature, decides placement, navigation, surface, action hierarchy and complexity budgets, and produces a precise implementation brief without coding unless explicitly…
full_unpackd_rep
Use when the task is to unpack a local reference repository into a Chinese structural topic page, update site navigation, stamp dates, and leave behind a reusable deconstruction note for the repo.
gen-zhihu-article
Generate Zhihu article in the style of 22-庖丁解牛专题页-知乎图文终版.md.
loloop
Use when a task should advance through repeated plan-driven loop cycles for an engineering project, paper, or long-running repo change. loloop wraps the official /loop idea with the repo's loop-in-loop method: read the current plan, inspect prior evolution notes, execute the current iteration, write a new evolution…
zhihu-publish
Use when the task is to publish a Zhihu article from Markdown using the local browser-automation pipeline in this repo. Covers the text-only publishing chain, the multimodal chain that uploads Markdown images into the Zhihu editor, cookie-based login checks, and choosing between the stable text script and the richer…