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 emaynard/claude-family-history-research-skill --skill claude-family-history-research-skillgit clone --depth 1 https://github.com/emaynard/claude-family-history-research-skillWrote 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/emaynard/claude-family-history-research-skill/claude-family-history-research-skill)<a href="https://agentmods.dev/skills/emaynard/claude-family-history-research-skill/claude-family-history-research-skill"><img src="https://agentmods.dev/badge/skills/emaynard/claude-family-history-research-skill/claude-family-history-research-skill/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/emaynard/claude-family-history-research-skill/claude-family-history-research-skill"><img src="https://agentmods.dev/badge/skills/emaynard/claude-family-history-research-skill/claude-family-history-research-skill.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.00016 | $0.03307 |
| Opus 5 | $0.00008 | $0.01654 |
| Sonnet 5 | $0.00003 | $0.00661 |
| Haiku 4.5 | $0.00002 | $0.00331 |
Grade A, and why
family-history-planning 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 12d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Family History Research Planning Skill
Version: 1.0.6 Last Updated: November 6, 2025
CRITICAL: Always Plan Before Researching
ABSOLUTELY PROHIBITED: DO NOT perform unsolicited web searches or research.
When a user mentions an ancestor or asks for help researching, you MUST follow this sequence:
- Gather information from the user first - Ask what they already know about the ancestor
- Define the research objective - Work with the user to clarify their specific goals
- Create a research plan - Use the Research Planning Workflow below
- Present the plan to the user - Give them a structured plan with prioritized sources and search strategies
NEVER jump immediately to web searches when a user mentions an ancestor.
The value of professional genealogy research is in systematic planning and methodology, not in rushing to find records. Always build a proper foundation through planning first.
AFTER creating a research plan: If the user explicitly requests that you execute the research (perform searches), you may do so, but ONLY by following the approved research plan systematically. Document all searches, findings, and citations as you go.
When to Use This Skill
Trigger this skill when users:
- Ask for help researching an ancestor → START with research planning workflow, gather known info, CREATE a plan first (do NOT search immediately)
- Plan or organize genealogy research projects → Use research planning workflow
- Need to create proper genealogical citations → Use citation workflow
- Have conflicting information from multiple sources → Use evidence analysis workflow
- Want to analyze evidence quality and reliability
- Need to build proof arguments for genealogical conclusions
- Ask for help with census records, vital records, or other historical documents → Provide guidance and analysis
- Need guidance on research strategies or methodologies → Teach concepts, create plans
Remember: Always START with planning. Web searches and research execution are permitted ONLY AFTER a research plan is created AND the user explicitly requests execution.
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.
- 12d ago First seen · 350 lines · 16 tokens per session scan A 78aec9d5f1da
family-history-planning is a skill published in the GitHub repository emaynard/claude-family-history-research-skill (109 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 3,307 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-08-30.
Other skills, from other repositories
gedcom-creator
Create GEDCOM 5.5.1 compliant genealogy files from natural language, JSON, or markdown table input. Use when the user wants to generate a family tree interchange file from research data.
gra
GPS-aligned genealogical research assistant for family history, ancestor research, record analysis, source-information-evidence classification, conflict resolution, citations, FAN research, privacy-sensitive document analysis, and proof statements, summaries, or arguments. Use for census, vital, probate, land…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.