Borrowing it
Nothing to install: this file belongs to dan-pugsley/life-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dan-pugsley/life-context/main/CLAUDE.mdgit clone --depth 1 https://github.com/dan-pugsley/life-contextWrote 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/dan-pugsley/life-context/claude-md)<a href="https://agentmods.dev/instructions/dan-pugsley/life-context/claude-md"><img src="https://agentmods.dev/badge/instructions/dan-pugsley/life-context/claude-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.1 | $0.00459 | $0.00459 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
life-context CLAUDE.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 7d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Life
Structured AI context store for personal life data. See _template.md for structural conventions.
Navigation
- Read root README.md for structure overview
- Read root profile.md for general user context
- Navigate to the domain relevant to the user's question
- Each folder's README.md orients you — read it before exploring further
Cross-cutting context
Before answering, consider whether sibling domains have relevant context. Check their READMEs to assess relevance.
Data entry
- Prefer AI-mediated data entry. Ask clarifying questions to ensure quality.
- If a profile.md is empty, offer to run the onboarding.md for that domain.
- Onboarding must run top-down: root profile before health, health before exercise, etc. Do not offer to skip or reorder — each level's profile informs the next.
- Reference parent profiles during onboarding to avoid redundant questions.
- Capture all useful information the user provides, even if not explicitly covered by the onboarding playbook. The playbook is a minimum, not a ceiling.
- When the user mentions supporting documents (MRI reports, diagnostic reports, images), proactively offer to import them into the relevant assets/ folder.
- The user may also edit files directly.
- Avoid writing computed values that go stale (e.g., write date of birth, not age). Let the AI calculate derived values at query time.
Living state vs. stable profile
Volatile facts — current injury restrictions, rehab progression stages, working loads, bodyweight, current training block — live in status.md, the single source of truth. Reference status.md from plans, READMEs, and workouts; never restate its contents. Keep it current as state changes. Stable facts (identity, history, baseline benchmarks, preferences) stay in profile.md.
Proactive maintenance
As new information arises — from events, issues, or conversation — keep the relevant profile.md, status.md, and README.md files up-to-date, including adding new children sections and updating summaries.
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.
- 7d ago First seen · 36 lines · 459 tokens per session scan A 529ab769d486
life-context CLAUDE.md is an instructions file published in the GitHub repository dan-pugsley/life-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 459 tokens to every session, about $0.0023 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-31.
Other instructions, from other repositories
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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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.