Borrowing it
Nothing to install: this file belongs to davidmosiah/delx-living-body. 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/davidmosiah/delx-living-body/main/AGENTS.mdgit clone --depth 1 https://github.com/davidmosiah/delx-living-bodyWrote 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/davidmosiah/delx-living-body/agents-md)<a href="https://agentmods.dev/instructions/davidmosiah/delx-living-body/agents-md"><img src="https://agentmods.dev/badge/instructions/davidmosiah/delx-living-body/agents-md/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/instructions/davidmosiah/delx-living-body/agents-md"><img src="https://agentmods.dev/badge/instructions/davidmosiah/delx-living-body/agents-md.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.00635 | $0.00635 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
delx-living-body AGENTS.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 10d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — delx-living-body
Quick reference for AI agents working with this MCP server.
What it is
A meta-MCP server: it composes other locally-installed Delx Wellness connectors (WHOOP, Oura, Garmin, etc.) into a single unified surface. Pure data composition — no LLM calls inside the server.
Tools (6)
living_body_status— which connectors are detected? Safe, no subprocess spawning.living_body_ask— main tool. Spawns children in parallel, returns synthesized answer. Requiresexplicit_user_intent: true.living_body_daily_brief— markdown brief from each connector's daily summary.living_body_compose_context— normalizeddelx-wellness-context/v1shape merged across sources.living_body_health_check— all 15 known connectors with install hints for missing ones.living_body_capabilities— self-description and per-connector availability matrix.
Recommended agent flow
- Call
living_body_capabilitiesonce at session start. - Call
living_body_statusto see what's installed. - For a specific question →
living_body_ask(always withexplicit_user_intent: true). - For raw merged context to hand off to another tool →
living_body_compose_context. - For a daily-stand-up-style summary →
living_body_daily_brief. - If sources are missing → show the user the
install_hintfromliving_body_health_check.
Rules
- Always pass
explicit_user_intent: truetoliving_body_ask. The tool spawns multiple subprocesses and should never be called speculatively. - Default privacy mode is
structured. Only userawwhen the user explicitly asks for vendor-native payloads. - Treat output as operational context, not medical advice.
- Don't ask the user to install every connector. Only suggest installing what's needed for the current question.
- The synthesizer is rule-based — its reasoning trace has stable
rule_ids (rec_low,bb_high, etc.). When you summarize for the user, you can reference these.
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.
- 10d ago First seen · 49 lines · 635 tokens per session scan A 239f1c4f33ca
delx-living-body AGENTS.md is an instructions file published in the GitHub repository davidmosiah/delx-living-body (0 stars, last pushed 3d ago), licensed MIT. It adds 635 tokens to every session, about $0.0032 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
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.
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).
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.
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.