tests-guard-intentional-workarounds

tests-guard-intentional-workarounds is a skill for Claude Code, Codex from divinevideo/divine-mobile. It costs 240 tokens per session (2,159 once invoked), scanned A, original, MPL-2.0.

A testing guideline for checking the test suite before removing code that looks redundant. It focuses on tests that document deliberate workarounds for platform bugs or timing problems.

In plain words
What is it for?
Use it during code cleanup or review before deleting calls, retries, or state updates that appear to do nothing.
Why use it?
A repeated or unnecessary-looking call may be required for an obscure runtime behavior, and removing it can break a case that tests do not obviously explain.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it during code cleanup or review before deleting calls, retries, or state updates that appear to do nothing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds
Install

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.

Any agent
npx skills add divinevideo/divine-mobile --skill tests-guard-intentional-workarounds
Clone the repo
git clone --depth 1 https://github.com/divinevideo/divine-mobile

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for tests-guard-intentional-workarounds

README.md
[![agentmods](https://agentmods.dev/badge/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds/github.svg)](https://agentmods.dev/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds)
Your own site
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds/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.

agentmods 80×15 button for tests-guard-intentional-workarounds

Your own site · 80×15
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/tests-guard-intentional-workarounds.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 240 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00240 $0.02159
Opus 5.5 $0.00096 $0.00864
Sonnet 5.5 $0.00048 $0.00432
Haiku 4.5 $0.00024 $0.00216

Measured 1mo ago against content hash 695003dbc3a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tests-guard-intentional-workarounds 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 1mo 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.

.agents/skills/tests-guard-intentional-workarounds/SKILL.md · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tests Guard Intentional Workarounds

Problem

You observe a production log line that looks clearly wrong — a function being called when its precondition already appears satisfied, a retry firing when the first attempt seemed to work, state being set to the value it already holds. Instinct says "this is a redundant no-op, I'll remove it." You remove it, run local tests (which may even pass if coverage is thin), push to CI, and a test fails with a title that describes exactly the behavior you just removed. The comment on that test explains a subtle platform bug or race condition that required the "redundant" call as a workaround.

The log line you reacted to wasn't evidence of a bug. It was evidence of the workaround executing correctly for the exact scenario it was designed for.

Context / Trigger Conditions

Apply this skill's caution when ANY of these hold:

  1. Redundant-looking call: You're about to wrap a call in if (!already_X) or delete it outright because logs show it firing when X is already true.
  2. Impossible state in logs: Logs show a state combination that seems logically impossible or contradictory (playing=true + positionMs=0 for seconds, isLoading=false + data still empty, etc.).
  3. "Why would anyone write this?": Reading code and you can't imagine a reason for a defensive check, extra await, or secondary call.
  4. Simplifying a conditional: A branch looks dead because you believe the condition can't be reached, or both branches look identical to you.
  5. Receiving a failing test: CI returns a failure with a test title that names exactly the behavior your change removed or modified.

Solution

Before touching the "redundant" code, run this five-step check:

Step 1: Grep for tests that assert the exact behavior

Search the test suite for the function name, the state you think is redundant, and any synonyms:

# Example: considering removing player.play() on rebuffer complete
grep -rn "player.play" test/ | grep -iE "already|even when|still|twice|redundant"
grep -rn "rebuffer.*play\|playing.*true.*play" test/

Read the full file on GitHub · 200 lines

Changes

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.

  1. 1mo ago First seen · 200 lines · 240 tokens per session scan A 695003dbc3a8

Subscribe to this mod's changes

tests-guard-intentional-workarounds is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 240 tokens to every session and 2,159 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens