mock-call-count-retry-fallback

mock-call-count-retry-fallback is a skill for Claude Code, Codex from divinevideo/divine-mobile. It costs 102 tokens per session (1,107 once invoked), scanned A, original, MPL-2.0.

A testing guide for updating mocks after adding retries, fallbacks, or alternative service calls. Mocks are test replacements for real dependencies, and call-count checks must match the new behavior.

In plain words
What is it for?
Use it to trace new code paths, stub fallback dependencies, and update exact call-count assertions in service tests.
Why use it?
It fixes tests that expect one number of calls but receive more, or fail because a newly used method has no configured mock response.

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 to trace new code paths, stub fallback dependencies, and update exact call-count assertions in service tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/divinevideo/divine-mobile/mock-call-count-retry-fallback
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 mock-call-count-retry-fallback
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 mock-call-count-retry-fallback

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/mock-call-count-retry-fallback"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/mock-call-count-retry-fallback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,107 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.00102 $0.01107
Opus 5.5 $0.00041 $0.00443
Sonnet 5.5 $0.00020 $0.00221
Haiku 4.5 $0.00010 $0.00111

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

Security

Grade A, and why

mock-call-count-retry-fallback 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/mock-call-count-retry-fallback/SKILL.md · 139 lines

How it starts

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

Mock Call Count Failures After Adding Retry/Fallback Logic

Problem

When you add retry logic, fallback mechanisms, or alternative code paths to a service, existing tests that verify exact mock method call counts will fail. The tests were written for the original behavior and don't account for the new retry/fallback calls.

Context / Trigger Conditions

  • Test fails with: Expected: <N>, Actual: <M> where M > N
  • Error message: "Unexpected number of calls"
  • MissingStubError: 'methodName' No stub was found which matches the arguments
  • You recently added:
    • Retry logic (e.g., retry after timeout)
    • Fallback mechanisms (e.g., try primary server, fall back to secondary)
    • Alternative code paths (e.g., try REST API, fall back to WebSocket)
  • The failing test uses verify(...).called(N) assertions

Solution

Step 1: Identify the New Code Paths

Trace through your new retry/fallback logic to understand:

  • How many times the mocked method will now be called
  • What new methods are being called that weren't before

Step 2: Mock New Dependencies

If your fallback code calls methods that weren't previously mocked:

// BEFORE: Only mocked the primary method
when(mockService.primaryMethod(any)).thenAnswer((_) async => 'result');

// AFTER: Also mock fallback-related methods
when(mockService.primaryMethod(any)).thenAnswer((_) async => 'result');
when(mockService.addFallbackServer(any)).thenAnswer((_) async => false);  // Graceful failure
when(mockService.queryFallback(any)).thenAnswer((_) async => []);

Step 3: Update Expected Call Counts

// BEFORE: Expected single call
verify(mockService.createSubscription(...)).called(1);

// AFTER: Expected calls = initial + retries
// Document WHY the count changed
verify(mockService.createSubscription(...)).called(2);  // initial + retry after fallback

Step 4: Add Comments Explaining the Count

// Verify subscription was created
// Note: With the indexer fallback logic, createSubscription is called twice:
// 1. First attempt via main relay batch fetch
// 2. Retry attempt after indexer fallback fails
verify(
  mockService.createSubscription(...),
).called(2);

Read the full file on GitHub · 139 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 · 139 lines · 102 tokens per session scan A bce2c38a66e4

Subscribe to this mod's changes

mock-call-count-retry-fallback is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 102 tokens to every session and 1,107 once invoked, about $0.0004 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