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/temporal-cortex/mcp/agents-mdgit clone --depth 1 https://github.com/temporal-cortex/mcpWhat 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 | $0.00538 | $0.00538 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
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 yesterday.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temporal Cortex MCP
Public documentation repo for the Temporal Cortex MCP server (@temporal-cortex/cortex-mcp). Source code is in a private repository — this repo contains user-facing docs, setup guides, integration examples, directory configs, and the Dockerfile.
Structure
README.md— Main user-facing docs (Q&A format: each section is a question)CHANGELOG.md— Release historydocs/— Setup guides (google-cloud-setup, outlook-setup, caldav-setup), tool reference, integration guides (CrewAI, OpenAI Agents SDK), architecture overviewexamples/— Integration examples:crewai/,langgraph/,openai-agents/, config snippets (claude-desktop.json, cursor.json, windsurf.json)Dockerfile— Multi-stage build wrapping the npm binarysmithery.yaml— Smithery directory configglama.json— Glama directory metadata (maintainers field only; Docker config is in Glama dashboard).mcp/server.json— MCP Registry metadataassets/— Icons and logos
Build & Test
No build system — this is a docs-only repo. To verify changes:
npx markdown-link-check README.md # check links
Ensure version numbers match across README.md, Dockerfile, and smithery.yaml.
Conventions
- Pin npm version (
@temporal-cortex/[email protected]) in Dockerfile, smithery.yaml, and.mcp/server.json - Do NOT pin npm versions in user-facing docs — always use
@temporal-cortex/cortex-mcp(latest) - Keep tool counts (18), layer numbers (0-4), and tool lists in sync with the source
- README uses Q&A format: each
##section is a question starting with "How", "What", "Can" - No pricing or business strategy content (public repo)
Adding Examples
Follow the pattern in examples/crewai/:
README.mdwith prerequisites, quick start, file descriptions.env.examplewith required environment variablesrequirements.txtfor Python dependencies- Both Local Mode (stdio) and Platform Mode (HTTP) variants where applicable
Boundaries
- Always: verify version numbers match across README, Dockerfile, smithery.yaml after version bumps
- Ask first: changing tool descriptions, parameter schemas, or layer assignments
- Never: include API keys, secrets, or pricing information
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.
- yesterday First seen · 48 lines · 538 tokens per session scan A a25342ea9408
mcp AGENTS.md is an instructions file published in the GitHub repository temporal-cortex/mcp (12 stars, last pushed 28d ago), licensed MIT. It adds 538 tokens to every session, about $0.0027 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-30.
Other instructions, from other repositories
google_workspace_mcp general.instructions.md
Instructions for taylorwilsdon/google_workspace_mcp, covering 📄 project context, 🎯 review goals & priorities, 🚦 low‑value feedback to skip, 🧭 review structure template and ✅ gmail.sendmessage – input schema issue.
mcp-server-apple-events GEMINI.md
Gemini CLI instructions for FradSer/mcp-server-apple-events, covering apple events mcp server, project overview, architecture, building and running and prerequisites.
cli AGENTS.md
Instructions for nylas/cli, covering ai coding agent guidelines, quick reference: shared helpers, quick reference: adding a new feature and quick reference: credential storage.
calendar-mcp copilot-instructions.md
Instructions for MarimerLLC/calendar-mcp, covering github copilot instructions for calendar-mcp, 📖 quick context, 🎯 project overview, 🏗️ project structure and 🛠️ technology stack.
olkcli CLAUDE.md
Instructions for rlrghb/olkcli, covering claude.md, what is this project?, quick reference, architecture and key patterns.
che-ical-mcp CLAUDE.md
Claude Code instructions for PsychQuant/che-ical-mcp, covering spectra instructions, use /spectra: skills when, workflow, parked changes and mcp 功能驗證的表面選擇（.claude/rules/mcp-binary-version-testing.md）.