condition-based-waiting

condition-based-waiting is a skill for Claude Code, Codex from rileyhilliard/agentrc. It costs 41 tokens per session (904 once invoked), scanned A, original, MIT.

A testing approach that waits for a real condition instead of pausing for a guessed amount of time. It is for asynchronous work, such as a request or background task that finishes later.

In plain words
What is it for?
Use it to replace arbitrary setTimeout or sleep calls in tests, wait for asynchronous operations, and investigate failures caused by timing. Keep fixed delays when testing timing features such as debouncing or throttling.
Why use it?
Fixed delays can make tests pass on one machine and fail on another or in continuous integration. Waiting for the result you actually need reduces these intermittent, or flaky, failures.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to replace arbitrary setTimeout or sleep calls in tests, wait for asynchronous operations, and investigate failures caused by timing. Keep fixed delays when testing timing features such as debouncing or throttling.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rileyhilliard/agentrc/condition-based-waiting
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 rileyhilliard/agentrc --skill condition-based-waiting
Clone the repo
git clone --depth 1 https://github.com/rileyhilliard/agentrc

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 condition-based-waiting

README.md
[![agentmods](https://agentmods.dev/badge/skills/rileyhilliard/agentrc/condition-based-waiting/github.svg)](https://agentmods.dev/skills/rileyhilliard/agentrc/condition-based-waiting)
Your own site
<a href="https://agentmods.dev/skills/rileyhilliard/agentrc/condition-based-waiting"><img src="https://agentmods.dev/badge/skills/rileyhilliard/agentrc/condition-based-waiting/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 condition-based-waiting

Your own site · 80×15
<a href="https://agentmods.dev/skills/rileyhilliard/agentrc/condition-based-waiting"><img src="https://agentmods.dev/badge/skills/rileyhilliard/agentrc/condition-based-waiting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 904 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.
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.00041 $0.00904
Opus 5.5 $0.00016 $0.00362
Sonnet 5.5 $0.00008 $0.00181
Haiku 4.5 $0.00004 $0.00090

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

Security

Grade A, and why

condition-based-waiting 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.

.agentrc/skills/condition-based-waiting/SKILL.md · 115 lines

How it starts

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

Condition-Based Waiting

Use with: writing-tests skill for overall test guidance. This skill focuses on timing-based flakiness.

Related: If tests pass alone but fail concurrently, the problem may be shared state, not timing. See fixing-flaky-tests skill for diagnosis.

Overview

Flaky tests often guess at timing with arbitrary delays. This creates race conditions where tests pass on fast machines but fail under load or in CI.

Core principle: Wait for the actual condition you care about, not a guess about how long it takes.

When to use

Test has arbitrary delay (setTimeout/sleep)?
    │
    ├─ Testing actual timing (debounce, throttle)?
    │   └─ Yes → Keep timeout, document WHY
    │
    └─ No → Replace with condition-based waiting

Use when:

  • Tests have arbitrary delays (setTimeout, sleep, time.sleep())
  • Tests are flaky with timing-related errors
  • Waiting for async operations to complete

Don't use when:

  • Testing actual timing behavior (debounce, throttle, intervals)
  • Problem is shared state between tests (use fixing-flaky-tests)

Core pattern

// Bad: Guessing at timing
await new Promise((r) => setTimeout(r, 50));
const result = getResult();
expect(result).toBeDefined();

// Good: Waiting for condition (returns the result)
const result = await waitFor(() => getResult(), 'result to be available');
expect(result).toBeDefined();

Implementation

Prefer framework built-ins when available:

  • Testing Library: findBy queries, waitFor
  • Playwright: auto-waiting, expect(locator).toBeVisible()
  • pytest: asyncio.wait_for, tenacity

Custom polling fallback when built-ins aren't enough:

async function waitFor<T>(
  condition: () => T | undefined | null | false,
  description: string,
  timeoutMs = 5000
): Promise<T> {
  const startTime = Date.now();

  while (true) {
    const result = condition();
    if (result) return result;

    if (Date.now() - startTime > timeoutMs) {
      throw new Error(`Timeout waiting for ${description} after ${timeoutMs}ms`);
    }

    await new Promise((r) => setTimeout(r, 50));  // Poll interval
  }
}

Read the full file on GitHub · 115 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 115 lines · 41 tokens per session scan A a1ace0d43f16

Subscribe to this mod's changes

condition-based-waiting is a skill published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 8mo ago), licensed MIT. It adds 41 tokens to every session and 904 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 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

critique

Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens