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 claim-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/claim-analysis)<a href="https://agentmods.dev/skills/yogsoth-ai/de-anthropocentric-research-engine/claim-analysis"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/claim-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/claim-analysis"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/claim-analysis.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.00037 | $0.01110 |
| Opus 5.5 | $0.00015 | $0.00444 |
| Sonnet 5.5 | $0.00007 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
claim-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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claim Analysis
Deep analysis of patent claim scope. Decomposes claim structure, maps element relationships, and assesses the breadth and strength of patent protection.
Purpose
Provide detailed claim-level analysis for a set of target patents. Determines protection scope, identifies claim vulnerabilities, and maps the relationship between independent and dependent claims.
Budget
| Metric | Target |
|---|---|
| Patent families analyzed | 30 |
| Claim parses | 30 |
| Web searches completed | 20 |
State Ledger
| Metric | Target | Current | % |
|---|---|---|---|
| Patent families analyzed | 30 | 0 | 0% |
| Claim parses completed | 30 | 0 | 0% |
| Web searches completed | 20 | 0 | 0% |
| Independent claims parsed | — | 0 | — |
| Claim elements extracted | — | 0 | — |
HARD-GATE: Cannot exit iteration loop until 80% of claim parses (24) and patent families (24) budget met.
Available Tactics
| Tactic | When to Use |
|---|---|
| claim-decomposition | Primary tactic — parse all claims and extract elements |
| patent-family-tracing | Find family members with different claim scope |
| classification-navigation | Understand technical context of claim elements |
Available SOPs
| SOP | Role in This Strategy |
|---|---|
| claim-parsing | Core SOP — parse claim syntax and extract elements |
| patent-query-formulation | Find related patents for scope comparison |
| citation-network-analysis | Identify patents that cite or are cited by target |
| legal-status-assessment | Confirm target patents are active |
| quality-scoring | Assess claim quality (breadth, specificity, support) |
| patent-synthesis | Produce claim analysis report |
Execution Guidance
- Target identification — Identify patents for deep claim analysis
- Legal status check — Confirm targets are active with
legal-status-assessment - Claim retrieval — Fetch full claim text via web searches
- Claim parsing — Use
claim-decompositiontactic for full structural analysis - Element extraction — Extract all claim elements and map relationships
- Scope assessment — Determine breadth of independent claims
- Vulnerability analysis — Identify potential design-arounds and invalidity arguments
- Family comparison — Check claim scope variations across jurisdictions
- Synthesis — Produce detailed claim analysis report
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 · 141 lines · 37 tokens per session scan A 376d34bde2af
claim-analysis is a skill published in the GitHub repository yogsoth-ai/de-anthropocentric-research-engine (505 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,110 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.