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/proscar87/oura-mcp/agents-mdgit clone --depth 1 https://github.com/proscar87/oura-mcpWrote 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/proscar87/oura-mcp/agents-md)<a href="https://agentmods.dev/instructions/proscar87/oura-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/proscar87/oura-mcp/agents-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.03186 | $0.03186 |
| Opus 5 | $0.01593 | $0.01593 |
| Sonnet 5 | $0.00637 | $0.00637 |
| Haiku 4.5 | $0.00319 | $0.00319 |
Grade A, and why
oura-mcp 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 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For the next agent
State as of 10 August 2026, after a twelve-round audit. Read this before touching anything.
What this is
An MCP server over the Oura v2 API. Its reason to exist is that Oura under-delivers without saying so, and that's corrected here.
Be careful how you tell that story, because it changed. An earlier version of
this file said the differentiator was pagination, and that "of the seven Oura
MCP servers, the most complete one doesn't paginate." That is no longer
true: benngermin/oura-mcp paginates properly, with a resumable cursor.
Pagination is table stakes now, not the edge. Don't repeat that line.
What does hold the project up are four silent failures of the same family, measured against the real API and corrected here:
| The failure | Where the fix lives | |
|---|---|---|
| 1 | Not following next_token returns a fraction. One local day of heartrate is 1,231 samples across 2 pages |
the pagination loop in the client |
| 2 | end_date is inconsistent across collections, and workout filters by UTC date while reporting day in local time |
MARGEN_DIAS and the trim step |
| 3 | latest=true where it doesn't apply → Oura returns the whole collection |
CON_ULTIMO, rejected before the network |
| 4 | fields=made_up → returns the complete record, no projection |
the ignored-fields check |
If anyone proposes "simplifying" any of those four, the answer is no. They are the product.
Where it's published
| GitHub | https://github.com/proscar87/oura-mcp — public, MIT, CI green |
| PyPI | https://pypi.org/project/mcp-oura/ — 0.1.0, 0.1.1, 0.2.0 |
| MCP registry | io.github.proscar87/oura-mcp v0.2.0, active, latest |
The install name is mcp-oura because oura-mcp was already taken on PyPI by a
0.1.0 package with no author and no repository. The imported module is still
oura_mcp.
How to publish a new version
# bump the number in pyproject.toml AND server.json — they must match
git tag v0.2.1 && git push origin v0.2.1
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 · 258 lines · 3,186 tokens per session scan A a2a191d366d1
oura-mcp AGENTS.md is an instructions file published in the GitHub repository proscar87/oura-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 3,186 tokens to every session, about $0.0159 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
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.
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.