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 confirm-failures-are-causally-linked-to-the-task-before-reportingit 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/confirm-failures-are-causally-linked-to-the-task-before-reportin)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/confirm-failures-are-causally-linked-to-the-task-before-reportin"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/confirm-failures-are-causally-linked-to-the-task-before-reportin/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/confirm-failures-are-causally-linked-to-the-task-before-reportin"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/confirm-failures-are-causally-linked-to-the-task-before-reportin.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.00029 | $0.00395 |
| Opus 5 | $0.00015 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
confirm-failures-are-causally-linked-to-the-task-before-reportin 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 9d 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
confirm failures are causally linked to the task before reporting rejection
Trigger
- (no explicit trigger metadata; cluster derived from category/tags)
Required Procedure
- confirm failures are causally linked to the task before reporting rejection
- separate pre-existing failures from task-introduced regressions in test reports
Forbidden Shortcuts
- (none recorded)
Delegation Template
When delegating a task affected by this skill, include:
SKILLS: file:.opencode/skills/generated/confirm-failures-are-causally-linked-to-the-task-before-reportin/SKILL.md
Reviewer Checks
- Verify each required action above appears in the diff.
Test Engineer Checks
- Add or update tests covering the trigger condition and the forbidden shortcut.
Source Knowledge IDs
- 820286b2-e40c-40f9-95d0-5ae2191c904f — When test_engineer reports failures, verify whether they are pre-existing and unrelated to the task scope before rejecting coder work — unrelated failures should not block task completion.
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.
- 9d ago First seen · 51 lines · 29 tokens per session scan A 36e6114ea5c8
confirm-failures-are-causally-linked-to-the-task-before-reportin is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 395 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
debug
Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be reproduced and proven before any fix. On-demand; callable mid-implement. NOT a feature to spec or build (that is specify/implement), NOT the lint/test gate (that is verify), NOT adversarial diff…
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
tdd-test-engineer
Use for test-first development, regression tests, flaky test debugging, coverage gaps, test strategy, CI failures, or converting bugs into minimal reproducible tests.
armada-verification
Mandatory pre-completion verification and evidence checklist before reporting done.
armada-tdd
Test-driven development for armada workers. Use before writing any implementation. Triggers on: TDD, failing test, test first, write a test.
debugging
Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack…