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 vivekkrishna/agentic-validation-skills --skill cige-stale-execution-repairgit clone --depth 1 https://github.com/vivekkrishna/agentic-validation-skillsWrote 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/vivekkrishna/agentic-validation-skills/cige-stale-execution-repair)<a href="https://agentmods.dev/skills/vivekkrishna/agentic-validation-skills/cige-stale-execution-repair"><img src="https://agentmods.dev/badge/skills/vivekkrishna/agentic-validation-skills/cige-stale-execution-repair/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/vivekkrishna/agentic-validation-skills/cige-stale-execution-repair"><img src="https://agentmods.dev/badge/skills/vivekkrishna/agentic-validation-skills/cige-stale-execution-repair.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.00878 |
| Opus 5.5 | $0.00022 | $0.00351 |
| Sonnet 5.5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
cige-stale-execution-repair 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CIGE: StaleExecutionAgent
Invoked by cige-failure-classification in two situations: Outdated Test Logic (Mode A — repair Execution[]) and a confirmed False Positive (Mode B — strengthen Guardrails). These are different repairs with different targets; do not conflate them.
When to invoke
- Mode A: Execution steps fail mid-flow (element not found, endpoint 404, workflow step no longer exists), and
specRefconfirms the intended outcome is still a valid product requirement. - Mode B: A run reported pass, but
cige-failure-classificationconfirmed it was a false positive — the evidence backing the pass was weak or gameable, not that the steps were wrong.
If neither condition is confirmed, do not use this skill.
Mode A — Repair Execution
- Read
Intent(the goal to preserve) andGuardrails(constraints that apply during repair). - Fetch
specRefto confirm the intended outcome is still a stated product requirement. - Inspect the current system state (live UI, API schema, current workflow) to understand what changed.
- Propose new
Execution[]steps that achieveIntentwithinGuardrails. - Dry-run the proposed steps to verify
Intentcan still be confirmed. - Surface the proposed diff to a human for approval — do not commit without sign-off.
Escalation rule: If no execution path can confirm Intent within the existing Guardrails, stop — this may be a misclassified Product Defect. Escalate to cige-product-defect-escalation rather than forcing a repair that technically passes.
Mode B — Strengthen Guardrails (the narrow exception)
A false positive means the steps "worked," but the pass shouldn't have counted — the test's evidence bar was too weak to catch an invalid end-state (e.g. it accepted UI success text without checking the backend record it implies). The fix targets Guardrails, not Execution.
- Read the false-positive report from
cige-failure-classification: what state was accepted as a pass, and why it shouldn't have been. - Propose an additive guardrail or evidence rule that would have caught this specific gap (e.g. "require backend order-service confirmation, not UI text alone").
- Never remove, weaken, or relax an existing guardrail as part of this repair — this mode only adds constraints, it never loosens them.
- Replay the test with the proposed guardrail in an isolated environment to confirm it still allows the true-positive path to pass and correctly blocks the false-positive path.
- Surface the proposed diff (old Guardrails, new Guardrails, the false positive it addresses) to a human for approval — do not commit without sign-off.
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.
- 1mo ago Changed · +5 lines · +56 tokens per session 8251daa7d1e5
- 1mo ago First seen · 49 lines · 0 tokens per session scan A 1df45939510e
cige-stale-execution-repair is a skill published in the GitHub repository vivekkrishna/agentic-validation-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 878 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.
Other skills, from other repositories
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
refactor-safely
Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…
debug
Investigate a bug to its root cause systematically — reproduce, trace the data flow, test one hypothesis at a time — then fix it with a regression test. Use when something is broken and the user has a symptom or error message to chase down.
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
debug-failing-test
Debug a failing test using an iterative logging approach, then clean up and document the learning.
stress-test
Stress test and harden code against extreme inputs, malformed data, and simulated infrastructure failures. Acts as a red team. Documents every crash, then hardens the boundary.