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 agentmods add instructions/airy10/gedcommcp/gemini-mdgit clone --depth 1 https://github.com/airy10/GedcomMCPWrote 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/instructions/airy10/gedcommcp/gemini-md)<a href="https://agentmods.dev/instructions/airy10/gedcommcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/airy10/gedcommcp/gemini-md.svg" alt="Measured on agentmods" 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 | $0.00774 | $0.00774 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
GedcomMCP GEMINI.md 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEDCOM MCP Project Overview
This project, "GedcomMCP," is an AI-driven server designed for creating, editing, and querying genealogical data from GEDCOM files. It aims to provide a robust platform for AI agents to interact with and manage genealogical information, enabling complex queries, data enrichment from external sources like Wikipedia, and the generation of detailed biographies and family trees. It's an experimental project focusing on leveraging AI for genealogical tasks.
Key Features:
- Load and parse GEDCOM files.
- Add/edit people, families, events, and places.
- Query people, families, events, and places.
- Find relationships between individuals.
- Generate family trees and timelines.
- Search across all genealogical data.
- Get detailed person and family information.
- Analyze genealogical data with statistics and duplicates detection.
Technologies:
The project is primarily written in Python, utilizing pytest for testing. It functions as an MCP (Multi-Agent Communication Protocol) server.
Building and Running
Installation:
- Clone the repository:
git clone https://github.com/airy10/GedcomMCP.git cd GedcomMCP - Install dependencies:
pip install -r requirements.txt
Usage:
To start the server:
- With default HTTP transport:
python src/gedcom_mcp/fastmcp_server.py - With stdio transport:
python src/gedcom_mcp/fastmcp_server.py --transport stdio - Specify host/port for HTTP transport:
python src/gedcom_mcp/fastmcp_server.py --host 0.0.0.0 --port 8080
Development Conventions
Project Structure:
src/gedcom_mcp/: Contains the main source code, includingfastmcp_server.py(main server application) and variousgedcom_*.pymodules for handling GEDCOM data.tests/: Houses unit tests for the project.prompts/: Contains prompt templates for various AI tasks.requirements.txt: Lists project dependencies.pyproject.toml: Build configuration.
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.
- 5d ago First seen · 98 lines · 774 tokens per session scan A f7f37b0a71b0
GedcomMCP GEMINI.md is an instructions file published in the GitHub repository airy10/GedcomMCP (14 stars, last pushed 1mo ago), licensed MIT. It adds 774 tokens to every session, about $0.0039 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.