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/huggingface/hf-mcp-server/agents-mdgit clone --depth 1 https://github.com/huggingface/hf-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/huggingface/hf-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/huggingface/hf-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/huggingface/hf-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 | $0.00673 | $0.00673 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
hf-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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hf-mcp-server AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Subagents
Project Structure & Module Organization
packages/app: MCP server plus management web UI. Server code lives inpackages/app/src/server, UI inpackages/app/src/web, and tests inpackages/app/test.packages/mcp: shared MCP tools/library consumed by the server. Source is inpackages/mcp/src, with tests inpackages/mcp/testand a few*.test.tsfiles co-located insrc.packages/e2e-python: Python-based end-to-end harnesses and fixtures.- Root-level docs and support files live in
docs/,docs-internal/,scripts/,spec/, andDockerfile.
Build, Test, and Development Commands
pnpm install: install workspace dependencies (Corepack-managed pnpm).pnpm build: build all workspace packages.pnpm dev: watch the MCP package and run the server with HMR.pnpm start: start the production server frompackages/app.pnpm lint,pnpm typecheck,pnpm format,pnpm test: run repo-wide checks.- Package-specific tests:
pnpm -C packages/app testorpnpm -C packages/mcp test. - Full local pipeline:
pnpm run buildrun(clean, build, lint, test, start).
Coding Style & Naming Conventions
- TypeScript ESM across packages.
- Prettier enforces tabs (
useTabs: true,tabWidth: 2), semicolons, single quotes, andprintWidth: 120. - ESLint rules are strict in
packages/mcpand server code (noany, consistent type imports, preferinterfacetype definitions). - Tests use
.test.tsor.spec.tsnaming.
Testing Guidelines
- Unit/integration tests run with Vitest in both
packages/appandpackages/mcp. - Run all tests with
pnpm testor package-specific commands above. - No explicit coverage gate is configured; add tests for new tools, transports, or formatting logic.
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.
- 4d ago First seen · 54 lines · 673 tokens per session scan A f8723bfac003
hf-mcp-server AGENTS.md is an instructions file published in the GitHub repository huggingface/hf-mcp-server (290 stars, last pushed 2d ago), licensed MIT. It adds 673 tokens to every session, about $0.0034 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
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.