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 update-or-delete-tests-that-assert-intentionally-removed-behaviogit 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/update-or-delete-tests-that-assert-intentionally-removed-behavio)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/update-or-delete-tests-that-assert-intentionally-removed-behavio"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/update-or-delete-tests-that-assert-intentionally-removed-behavio/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/update-or-delete-tests-that-assert-intentionally-removed-behavio"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/update-or-delete-tests-that-assert-intentionally-removed-behavio.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.00024 | $0.00415 |
| Opus 5.5 | $0.00010 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
update-or-delete-tests-that-assert-intentionally-removed-behavio 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 18d 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
update or delete tests that assert intentionally removed behavior
Trigger
- (no explicit trigger metadata; cluster derived from category/tags)
Required Procedure
- update or delete tests that assert intentionally removed behavior
- verify no test asserts behavior the changeset deliberately removes
Forbidden Shortcuts
- (none recorded)
Delegation Template
When delegating a task affected by this skill, include:
SKILLS: file:.opencode/skills/generated/update-or-delete-tests-that-assert-intentionally-removed-behavio/SKILL.md
Reviewer Checks
- grep test files for removed code patterns (e.g. Date.now() timestamps, deprecated API calls)
- run full test suite after changes and classify every failure as regression vs stale-test
Test Engineer Checks
- Add or update tests covering the trigger condition and the forbidden shortcut.
Source Knowledge IDs
- ca60f911-c1d4-4fb1-8245-44bf6cf95045 — When intentionally removing a code path, update or delete all tests asserting the old behavior in the same changeset — stale assertions that validate removed behavior count as test failures, not expected regressions.
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.
- 18d ago Changed · -1 lines 2ffc1f06c6b9
- 1mo ago First seen · 52 lines · 24 tokens per session scan A e143bb27ec43
update-or-delete-tests-that-assert-intentionally-removed-behavio is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (516 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 415 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
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
deflake
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.