Borrowing it
Nothing to install: this file belongs to cyanheads/openalex-mcp-server. 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/cyanheads/openalex-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/cyanheads/openalex-mcp-serverWrote 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/cyanheads/openalex-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/cyanheads/openalex-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/openalex-mcp-server/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.05323 | $0.05323 |
| Opus 5 | $0.02661 | $0.02661 |
| Sonnet 5 | $0.01065 | $0.01065 |
| Haiku 4.5 | $0.00532 | $0.00532 |
Grade A, and why
openalex-mcp-server 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 2d 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.
This is a copy
70% identical to obsidian-mcp-server AGENTS.md — 367 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: openalex-mcp-server
Version: 0.7.10
Framework: @cyanheads/mcp-ts-core ^0.12.5
Engines: Bun ≥1.3.0, Node ≥24.0.0
MCP SDK: @modelcontextprotocol/server ^2.0.0
Zod: ^4.5.4
Read the framework docs first:
node_modules/@cyanheads/mcp-ts-core/CLAUDE.mdcontains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
Domain
OpenAlex is a fully open catalog of the global research system — 270M+ works, 90M+ authors, 100K+ sources. CC0 data, no API key required (email address optional for polite pool access).
Entity types: works, authors, sources, institutions, topics, keywords, publishers, funders. All share a uniform API (list/filter, search, get-by-ID, group-by, autocomplete).
Critical workflow: Names are ambiguous, IDs are not. Always resolve names to IDs first via openalex_resolve_name before using them in filters.
Reference docs: README.md covers the current tool and prompt surface; docs/tree.md shows the current repository layout.
MCP Surface
| Type | Name | Purpose |
|---|---|---|
| Tool | openalex_search_entities |
Search, filter, sort, or retrieve by ID |
| Tool | openalex_analyze_trends |
Group-by aggregation for trends/distributions |
| Tool | openalex_resolve_name |
Name-to-ID resolution via autocomplete |
| Tool | openalex_get_citation_graph |
One-hop citation graph traversal (cites/cited_by/related_to) |
| Tool | openalex_describe_fields |
List valid filter/group_by/select field names per entity type |
| Prompt | openalex_literature_review |
Guided systematic literature search workflow |
| Prompt | openalex_research_landscape |
Quantitative research landscape analysis |
No resources — entity lookups need select for payload control, which fits tools better than URI templates.
Config
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.
- 2d ago Changed 45b3581a2b78
- 6d ago First seen · 366 lines · 5,323 tokens per session scan A afc993fbe910
openalex-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/openalex-mcp-server (14 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5,323 tokens to every session, about $0.0266 per session on Opus 5. A static security scan graded it A with 0 findings. It is 70% identical to obsidian-mcp-server AGENTS.md, differing in 367 lines, and is treated as a copy.
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.
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.