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 orenluxy/fable-method --skill convergence-guardgit clone --depth 1 https://github.com/orenluxy/fable-methodWrote 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/orenluxy/fable-method/convergence-guard)<a href="https://agentmods.dev/skills/orenluxy/fable-method/convergence-guard"><img src="https://agentmods.dev/badge/skills/orenluxy/fable-method/convergence-guard/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/orenluxy/fable-method/convergence-guard"><img src="https://agentmods.dev/badge/skills/orenluxy/fable-method/convergence-guard.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.00074 | $0.00590 |
| Opus 5.5 | $0.00030 | $0.00236 |
| Sonnet 5.5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
convergence-guard 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convergence Guard (stoploss)
Principle: the most expensive failure mode in agentic work is the fix-loop — repeatedly patching symptoms of a wrong plan. Tokens spent in a fix-loop are worse than wasted: they deepen commitment to a broken approach. This skill defines when to STOP.
External tool detection — check first
At session start (the PostToolUse hook does this automatically too): if a stoploss command exists on PATH or a stoploss.config.* file exists in the project, the user has a dedicated stoploss tool. Defer to it: run stoploss report (or its documented equivalent) when checking convergence, and treat its thresholds as authoritative over the defaults below.
Native thresholds (when no external tool is present)
Track mentally and via IMPLEMENTATION_NOTES.md:
- Same-file churn: the same file edited 5+ times in one session without its tests turning green → WARNING: state it explicitly and re-examine the approach before the next edit. 8+ edits → STOP.
- Three-strike rule: 3 consecutive fix attempts for the same failing test/behavior, each failing → STOP. Attempt #4 with the same strategy is forbidden.
- Deviation pressure: 3+ entries under Deviations in IMPLEMENTATION_NOTES.md touching the same subsystem → STOP.
- Scope creep: the session has touched 2x more files than the plan anticipated → pause and re-confirm scope with the user.
What STOP means
STOP is not "give up." It is a mandatory replan checkpoint:
- Freeze edits. No more code changes.
- Summarize for the user: what was attempted, what failed each time, what the failures have in common.
- State the hypothesis the fix-loop was implicitly betting on, and why the evidence now contradicts it.
- Propose 2 alternative approaches (different strategy, not different patch), with cost estimates.
- Wait for the user's call. Resuming the old strategy requires their explicit approval.
Anti-patterns
- "One more try" past a threshold. Thresholds exist precisely because in-the-loop judgment is compromised in a loop.
- Silently resetting the counter after a partial success. A test flipping green then red again counts as a strike, not a reset.
- Treating STOP as failure. Detecting a wrong plan after 3 attempts instead of 15 is the system succeeding.
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 First seen · 38 lines · 74 tokens per session scan A 72fcea4a84b4
convergence-guard is a skill published in the GitHub repository orenluxy/fable-method (2 stars, last pushed 15d ago), licensed MIT. It adds 74 tokens to every session and 590 once invoked, about $0.0003 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
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
tang-rou
Ative TANG-ROU (Soft Mist) quando o usuário nomear TANG-ROU ou pedir desenvolvimento, correção, auditoria, otimização ou planejamento de Foundry VTT e programação aplicada: macros, módulos, sistemas, CSB, Combat Tracker Dock, Midi-QOL, DAE, Sequencer, Warp Gate, Active Effects, hooks, compêndios, fichas homebrew, erro…
performance-profiler
Tier: POWERFUL Category: Engineering Domain: Performance Engineering.