Borrowing it
Nothing to install: this file belongs to thalovant/thalovant-mcp. 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/thalovant/thalovant-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/thalovant/thalovant-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/thalovant/thalovant-mcp/agents-md)<a href="https://agentmods.dev/instructions/thalovant/thalovant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/thalovant/thalovant-mcp/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/thalovant/thalovant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/thalovant/thalovant-mcp/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.00283 | $0.00283 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
thalovant-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 10d 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.
What it actually says
Repository instructions
This repository is a first-class consumer of the Thalovant control-plane and hub runtime APIs. Read the platform contracts in ../infra-manifests/docs/thalovant-platform/ when available.
Rules:
- Use only supported public API/protocol contracts; do not bypass them with direct Kubernetes or database access.
- For every affected API/protocol change, update tool input/output schemas, validation, handlers, examples, tests, README, changelog, and compatibility metadata together.
- Keep
package.json,server.json, npm package, OCI image, and configured MCP registry metadata on the same release version. - Consume a compatible published
@thalovant/sdkversion and preserve backward compatibility through the API migration window. - Update affected
docs.thalovant.comMCP setup, tool reference, examples, and compatibility pages in the same release train. - Prefer explicit, narrowly scoped tools and shared helpers only where reuse is demonstrated. Do not mirror the entire API mechanically or add speculative dependencies.
Validate with npm ci, npm run typecheck, npm run build, npm test, npm run test:smoke, and npm run test:http. Build before the transport tests because they execute dist/index.js. An affected release is complete only after clean-install stdio and Streamable HTTP smoke tests pass against the published npm/OCI artifacts.
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.
- 10d ago First seen · 15 lines · 283 tokens per session scan A 45dc70aa2a74
thalovant-mcp AGENTS.md is an instructions file published in the GitHub repository thalovant/thalovant-mcp (0 stars, last pushed today), licensed MIT. It adds 283 tokens to every session, about $0.0014 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).
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.
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.