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 yogsoth-ai/de-anthropocentric-research-engine --skill boundary-probinggit clone --depth 1 https://github.com/yogsoth-ai/de-anthropocentric-research-engineWrote 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/de-anthropocentric-research-engine/boundary-probing)<a href="https://agentmods.dev/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-probing"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-probing/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/yogsoth-ai/de-anthropocentric-research-engine/boundary-probing"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-probing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00418 |
| Opus 5 | $0.00013 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
boundary-probing 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- boundary-probing — 100% identical, 0 lines differ
What it actually says
Boundary Probing
Orchestration Steps
- Receive claim and parameter context from strategy
- Dispatch
parameter-space-mappingto identify all dimensions - For each dimension, dispatch
extreme-value-generation:- Minimum, maximum, zero, negative, overflow
- Type boundaries (empty, null, singleton, infinite)
- Dispatch
breakpoint-detectionat each extreme value - Record pass/fail for each probe point
- Dispatch
validity-envelope-constructionto synthesize boundaries
Subagents
- parameter-space-mapping
- extreme-value-generation
- breakpoint-detection
- validity-envelope-construction
Termination Conditions
- All dimensions probed at all boundary values (complete)
- Breakpoint found in critical dimension (early report)
- Budget exhausted (report partial envelope)
- Dimension count exceeds budget (prioritize by sensitivity)
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| breakpoint-detection | Test a claim at extreme parameter values and detect the precise point where it breaks down. |
| extreme-value-generation | Generate boundary and extreme test values for a given parameter dimension to stress-test claims. |
| parameter-space-mapping | Identify all parameter dimensions along which a claim's validity might vary. |
| stress-test-validity-envelope-construction | Synthesize breakpoints across dimensions into a coherent validity envelope for a claim. |
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.
- 8d ago First seen · 59 lines · 25 tokens per session scan A 43cbe0de1242
boundary-probing is a skill published in the GitHub repository yogsoth-ai/de-anthropocentric-research-engine (462 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 418 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-09-03.
Other skills, from other repositories
test-iterate-loop
Autonomously diagnose a codebase, apply minimal fixes, and rerun tests until they pass or a real blocker is reached. Use when the user explicitly requests an iterative fix-until-green loop across Python, R, Julia, or HPC workflows.
superpowers-zh
Use when constraining AI coding with Chinese TDD methodology, systematic debugging, code review, and verification workflows. Superpowers-zh: Chinese adaptation of the Superpowers AI-assisted programming skills and methodologies.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
fix-failing-tests
Iteratively fix all failing tests until the test suite is green.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.