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 agentmods add skills/hkuds/openspace/detect-zero-iteration-failuresnpx skills add HKUDS/OpenSpace --skill detect-zero-iteration-failuresgit clone --depth 1 https://github.com/HKUDS/OpenSpaceWrote 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/hkuds/openspace/detect-zero-iteration-failures)<a href="https://agentmods.dev/skills/hkuds/openspace/detect-zero-iteration-failures"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/detect-zero-iteration-failures.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00023 | $0.01093 |
| Opus 5 | $0.00012 | $0.00547 |
| Sonnet 5 | $0.00005 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
detect-zero-iteration-failures 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect Zero-Iteration Failures
This skill helps identify and properly categorize agent failures that occur before any task execution begins. These failures require system-level investigation rather than agent-level debugging.
When to Apply
Use this skill when analyzing agent task executions where:
- Iteration count is 0 - The agent completed zero iterations
- No tool usage - No tools were invoked during the execution
- No artifacts created - No files, documents, or outputs were produced
- Minimal or no conversation log - Only the user instruction exists, with no agent responses
Identification Checklist
Check the following indicators to confirm a zero-iteration failure:
[ ] Iterations reported: 0
[ ] Tool invocations: None
[ ] Files created: None
[ ] Conversation turns: 1 (user instruction only)
[ ] Agent self-report: Indicates failure before execution began
Failure Categories
Zero-iteration failures typically indicate one of these pre-execution issues:
| Category | Description | Investigation Focus |
|---|---|---|
| Initialization crash | Agent failed during setup | System logs, environment config |
| Environment issue | Missing dependencies or resources | Infrastructure, permissions |
| Prompt parsing error | Input could not be processed | Prompt format, encoding |
| Resource exhaustion | Quota or limits exceeded | System capacity, rate limits |
Diagnostic Steps
Step 1: Verify Zero-Iteration Indicators
def is_zero_iteration_failure(execution_log):
"""Check if execution shows zero-iteration failure pattern."""
indicators = {
'iterations': execution_log.get('iterations', 0) == 0,
'tools_used': len(execution_log.get('tool_calls', [])) == 0,
'artifacts': len(execution_log.get('files_created', [])) == 0,
'conversation_length': len(execution_log.get('messages', [])) <= 1
}
return all(indicators.values())
Step 2: Check System-Level Indicators
What ships with it
1 file 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.
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.
- 4d ago First seen · 152 lines · 23 tokens per session scan A 963d701eb2e6
detect-zero-iteration-failures is a skill published in the GitHub repository HKUDS/OpenSpace (7,501 stars, last pushed 22d ago), licensed MIT. It adds 23 tokens to every session and 1,093 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…