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 restore-internals-seams-in-finally-blocks-after-each-testgit 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/restore-internals-seams-in-finally-blocks-after-each-test)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/restore-internals-seams-in-finally-blocks-after-each-test"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/restore-internals-seams-in-finally-blocks-after-each-test/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/restore-internals-seams-in-finally-blocks-after-each-test"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/restore-internals-seams-in-finally-blocks-after-each-test.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.00026 | $0.00390 |
| Opus 5.5 | $0.00010 | $0.00156 |
| Sonnet 5.5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
restore-internals-seams-in-finally-blocks-after-each-test 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 14d 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
restore _internals seams in finally blocks after each test
Trigger
- (no explicit trigger metadata; cluster derived from category/tags)
Required Procedure
- restore _internals seams in finally blocks after each test
- verify seam restoration in afterEach
Forbidden Shortcuts
- (none recorded)
Delegation Template
When delegating a task affected by this skill, include:
SKILLS: file:.opencode/skills/generated/restore-internals-seams-in-finally-blocks-after-each-test/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
- 5ef666bf-7c7b-4990-b652-20782bf9c866 — When testing error-handling paths via _internals DI seams, always restore original implementations in a finally block to prevent cross-test pollution that causes cascading failures in Bun's shared test-runner process
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.
- 14d ago Changed · -1 lines e5c42e1a2ea6
- 1mo ago First seen · 51 lines · 26 tokens per session scan A 5630c0dde8c2
restore-internals-seams-in-finally-blocks-after-each-test is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (513 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 5.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
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…
vc:autoresearch
Autonomous iterative optimization loop for measurable metrics like coverage, performance, or bundle size. Use when repeated experiments can be judged by a mechanical score.
testing-strategy
Test selection and scope guidance: tiers, marks, batching, cross-module regressions. Loaded by the testing rule module. Triggers: 'which tests should I run', 'test scope', 'test tiers'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
react-testing
Testing Library for React 19 - render, screen, userEvent, waitFor, Suspense. Use when writing tests for React components with Vitest.
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).