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/yogsoth-ai/stress-test/breakpoint-detectionnpx skills add yogsoth-ai/stress-test --skill breakpoint-detectiongit clone --depth 1 https://github.com/yogsoth-ai/stress-testWrote 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/yogsoth-ai/stress-test/breakpoint-detection)<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/breakpoint-detection"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/breakpoint-detection.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.1 | $0.00022 | $0.00151 |
| Opus 5 | $0.00011 | $0.00076 |
| Sonnet 5 | $0.00004 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
breakpoint-detection 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 5d 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.
This is a copy
100% identical to breakpoint-detection — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Breakpoint Detection
Subagent that evaluates a claim at extreme values to find the precise breakpoint where validity fails.
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent. |
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.
- 5d ago First seen · 27 lines · 22 tokens per session scan A 075ffcc85389
breakpoint-detection is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 151 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to breakpoint-detection, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
research-ideation
Quant-focused research ideation pipeline: scope selection (3 stages) → anchor-first literature grounding → single-core idea generation → iterative refinement → ELO tournament ranking (Final = N+R+C−D) → update evo-memory → user selects direction → expand into manuscript-quality proposal. Optimized for incremental…
quant-experiment-runtime
Quant research experiment executor: discover an offline source database under the workdir's code-repo, build a panel, run a Research Artifact's entry point to compute research-object values, and evaluate IC/ICIR/RANKIC/coverage metrics. Runtime = Experiment Executor; it runs a Research Artifact via a Python-native…
local-paper-navigator
Find and read papers from the local papers library (repo papers/, mounted at /papers/). Three native tools form a reading funnel: papersearch (one line per paper), paperread (card + section outline), papersection (one verbatim section — the only full-text access). Use when: find papers in the local library, read a…
experiment-pipeline
Guides structured 4-stage experiment execution with attempt budgets and gate conditions: Stage 1 initial implementation (reproduce baseline), Stage 2 hyperparameter tuning, Stage 3 proposed method validation, Stage 4 ablation study. Integrates with evo-memory (load prior strategies, trigger IVE/ESE) and…
paper-review
Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: 5-aspect checklist (contribution sufficiency, writing clarity, results quality, testing completeness, method design), counterintuitive protocol (reject-first simulation, delete unsupported claims, score trust…
labrat-operator
Use when operating a labrat lab with Codex: checking health, choosing the next phase prompt, supervising runtime cycles, auditing candidates, synthesizing recent evaluations, or writing checkpoint notes.