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-analysisgit 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-analysis)<a href="https://agentmods.dev/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-analysis"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-analysis/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-analysis"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/boundary-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 56 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00042 | $0.00792 |
| Opus 5 | $0.00021 | $0.00396 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
boundary-analysis 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 9d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boundary Analysis
Probe where methods fail — validity envelopes, robustness, failure modes, scaling limits.
Design Philosophy
This campaign is a strategy book — CC reads, internalizes, and autonomously constructs an approach. The SKILL.md files are textbooks, not scripts.
Strategy Routing
| Signal | Strategy |
|---|---|
| Valid conditions, applicability range, multi-axis variation, degradation curves | → validity-envelope-mapping |
| Cross-method consistency, multi-model convergence, Wimsatt robustness | → robustness-testing |
| System boundaries, inclusion/exclusion, CSH critique | → boundary-critique |
| Failure modes, boundary inputs, distribution shift, adversarial | → failure-mode-analysis |
| Scaling limits, scaling law, behavioral phase transitions, capacity | → scaling-frontier |
Available Tactics
- multi-model-convergence — Wimsatt-style cross-validation
- systematic-perturbation — multi-axis validity probing
- failure-mode-cataloging — systematic failure taxonomy
Available SOPs
Import (5): web-search, web-research, paper-overview, paper-search, paper-research
Subagent (11): assumption-enumeration, alternative-model-generation, convergence-assessment, fragility-flagging, variation-axis-definition, controlled-perturbation, validity-envelope-construction, edge-case-generation, failure-clustering, scaling-regime-detection, boundary-synthesis
Shared (1): evidence-synthesis
Context Management
context-checkpoint after each strategy completes.
Available Strategies
Optional, no fixed order; the final leaf is always a sop.
| Strategy | When to use |
|---|---|
| boundary-critique | Apply CSH boundary critique — what is included/excluded, who benefits/is harmed, what expertise is privileged/marginalized. Identifies opportunities at the boundaries. |
| deep-insight-validity-envelope-mapping | Map multi-dimensional validity envelopes — define variation axes, perturb systematically, measure degradation, construct boundary surface. |
| failure-mode-analysis | Systematically catalog failure modes — generate edge cases, observe failures, cluster by mechanism, identify triggers and frequency. |
| robustness-testing | Test conclusion robustness via multi-model convergence — enumerate assumptions, generate alternatives, compare results, flag fragile conclusions. |
| scaling-frontier | Analyze behavior across scales — detect regime changes, identify capacity limits, fit scaling laws within regimes. |
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.
- 9d ago First seen · 81 lines · 42 tokens per session scan A 4764a8407616
boundary-analysis is a skill published in the GitHub repository yogsoth-ai/de-anthropocentric-research-engine (462 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 792 once invoked, about $0.0002 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
omnisci
Run OmniScientist end to end in the OmniScientist CLI using DeepSeek V4 Flash. Turn raw research data (images, signals, audio, video, 3-D, tables, or graphs) and an open direction into perceived evidence, a falsifiable hypothesis, recorded analysis, real citations, a gated candidate paper, PDF, and Overleaf bundle.…
lit-review-assistant
Search, summarize, and synthesize economics literature.
papers-reading-skill
Evidence-grounded AI research workflow for turning supplied economics, finance, management, and social-science papers or structured records into versioned PaperReading artifacts. Use when Codex must ingest text, Markdown, or a text-based PDF; separate source-grounded claims from researcher analysis; bind findings to…
academic-figure-generation
Generates publication-quality academic figures (framework diagrams, pipeline illustrations, system architectures, method overviews) from a paper's method text and a target caption, using a local PaperBanana multi-agent pipeline (Retriever → Planner → Stylist → Visualizer → Critic).
academic-paper-reviewer
Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on…
research-log
Record, manage, and query research experiment logs. Use when the user wants to log an experiment result, amend an existing entry, view recent logs, rebuild the index, or plan, execute, repeat, or diagnose research in a project containing docs/researchlog/. Triggers on phrases like "log this experiment", "record…