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/jesse-smith/searchloinc/claude-mdgit clone --depth 1 https://github.com/jesse-smith/searchloincWrote 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/jesse-smith/searchloinc/claude-md)<a href="https://agentmods.dev/instructions/jesse-smith/searchloinc/claude-md"><img src="https://agentmods.dev/badge/instructions/jesse-smith/searchloinc/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.01019 | $0.01019 |
| Opus 5 | $0.00509 | $0.00509 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
searchloinc 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
A thin MCP server wrapping the LOINC Search API so LLMs can search LOINC the same way a human does via the loinc.org/search UI. Eventually intended to run as a Databricks app.
Stack: Python (FastMCP), managed with uv. Credentials via environment variables.
LOINC Search API contract
This wraps the documented Search API (https://loinc.regenstrief.org/searchapi/) — the
same backend the loinc.org/search UI calls. Do not confuse it with the FHIR terminology
service (fhir.loinc.org), which is a different, structured code-system API that does NOT
reproduce the UI's free-text relevance ranking.
- Docs: https://loinc.org/kb/api/search-api/ · auth: https://loinc.org/kb/api/auth/ · syntax: https://loinc.org/kb/search/basic and /kb/search/advanced-search-syntax
- Four scoped GET endpoints — one MCP tool each is the intended design:
/loincs(terms),/answerlists,/parts,/groups - Query params:
query(required),rows,offset,sortorder(field asc|desc),language(int code fromLinguisticVariants.csv),includefiltercounts(bool) - Auth: HTTP Basic with a LOINC username/password (register on loinc.org). Never
hardcode — read
LOINC_USERNAME/LOINC_PASSWORDfrom the environment.
Development
uv syncto install (--extra devfor ruff/pytest);uv run <cmd>to run inside the project venv (do not use systempython3).toon-formatis a prerelease pin (>=0.9.0b1).- Run the server:
uv run python -m searchloinc(stdio transport). Or install it as a standalone command withuv tool install .and runsearchloinc(same stdio server via the[project.scripts]entry point →searchloinc.__main__:main); pass creds through the MCP client'senvblock, since the installed command has no--env-file. - Test a live query end-to-end with the
/loinc-searchskill before trusting wrapper output. - Format/lint with
ruff(viauv run ruff format/uv run ruff check). Note: a save hook runsruff --fix, which strips not-yet-used imports — add an import in the same edit as its first use, or it vanishes before you reference it.
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.
- 4d ago First seen · 68 lines · 1,019 tokens per session scan A c8e21a64cb35
searchloinc CLAUDE.md is an instructions file published in the GitHub repository jesse-smith/searchloinc (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,019 tokens to every session, about $0.0051 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).
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.
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).