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 generate-candidate-directionsgit 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/generate-candidate-directions)<a href="https://agentmods.dev/skills/yogsoth-ai/de-anthropocentric-research-engine/generate-candidate-directions"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/generate-candidate-directions/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/generate-candidate-directions"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/generate-candidate-directions.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.00024 | $0.00292 |
| Opus 5.5 | $0.00010 | $0.00117 |
| Sonnet 5.5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
generate-candidate-directions 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.
What it actually says
generate-candidate-directions
Purpose
Generate diverse candidate research fields or subfields consistent with context while permitting deliberate boundary crossing.
Input contract
required: [research_intent, scope_anchor]
optional: [seed_evidence, actor_profile, constraints, neighboring_domains]
constraints: [each candidate must state fit, boundary crossing, and evidence needs]
Procedure
- Extract the problem mechanism, outcome, and scope anchor.
- Generate candidates within the anchor and from adjacent domains.
- Record the transfer or boundary-crossing rationale for each candidate.
- Remove duplicates while preserving materially different mechanisms.
If candidate fields are diverse enough for comparative characterization, consider synthesize-field-panorama as the next tactic.
Output contract
produces: [candidate_directions, fit_rationales, boundary_crossings, evidence_questions]
delta_fields: [findings, hypothesis_updates, uncertainties, open_questions, recommended_jumps]
Quality gates
- Candidates are distinct by mechanism or evidence opportunity.
- Speculative candidates are labeled as such.
Failure and counterexamples
Do not equate popularity with fit or generate a list of fields without a boundary rationale.
Provenance map
resolved: generate-candidate-fields
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 · 48 lines · 24 tokens per session scan A d16ff21871bf
generate-candidate-directions is a skill published in the GitHub repository yogsoth-ai/de-anthropocentric-research-engine (505 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 292 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-24.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…