Borrowing it
Nothing to install: this file belongs to edithatogo/healthpoint-rs. 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/edithatogo/healthpoint-rs/main/AGENTS.mdgit clone --depth 1 https://github.com/edithatogo/healthpoint-rsWrote 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/edithatogo/healthpoint-rs/agents-md)<a href="https://agentmods.dev/instructions/edithatogo/healthpoint-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/edithatogo/healthpoint-rs/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/edithatogo/healthpoint-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/edithatogo/healthpoint-rs/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.00572 | $0.00572 |
| Opus 5 | $0.00286 | $0.00286 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
healthpoint-rs 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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project structure
This repository is a Rust workspace for Healthpoint API tooling.
conductor.jsondeclares setup/run/context entrypoints used by Conductor.bin/conductor-setupperforms metadata preflight and full Cargo setup when Cargo is available.script/serverstarts the read-only MCP server from source.conductor/stores state, decisions, checkpoints, and implementation tracks.crates/healthpoint-core/contains domain records, query model, validation, redaction, provenance, and resource URIs.crates/healthpoint-fhir/contains tolerant FHIR JSON mappers.crates/healthpoint-client/contains the async HTTP client.crates/healthpoint-cli/defines thehealthpointcommand surface.crates/healthpoint-mcp/defines the read-only MCP server.crates/healthpoint-export/contains export helpers and manifests.crates/healthpoint-osd-adapter/contains future open_social_data tabular views.crates/healthpoint-testkit/contains synthetic fixtures only.
Build, test, and development commands
Run from the repository root:
bin/conductor-setup
cargo fmt --all --check
cargo check --workspace --all-targets
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings
cargo run -p healthpoint-cli -- fixture services --format human
cargo run -p healthpoint-cli -- doctor
cargo run -p healthpoint-mcp
If Cargo is unavailable and you only need metadata validation:
CONDUCTOR_ALLOW_NO_CARGO=1 bin/conductor-setup
Coding style
Use safe Rust only. Keep command handlers thin and delegate domain logic to crates. Preserve raw FHIR JSON on typed records. Avoid adding heavyweight dependencies to healthpoint-core.
Testing guidelines
- Use synthetic fixtures in CI.
- Do not commit real Healthpoint API responses.
- Gate live tests behind explicit environment variables and document metadata-only findings.
- Before changing FHIR mapping, update fixtures and schema/adapter docs.
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.
- 9d ago First seen · 62 lines · 572 tokens per session scan A 3ba53df872fa
healthpoint-rs AGENTS.md is an instructions file published in the GitHub repository edithatogo/healthpoint-rs (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 572 tokens to every session, about $0.0029 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).
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.