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/humanforai/humanforai-mcp/agents-mdgit clone --depth 1 https://github.com/humanforai/humanforai-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/humanforai/humanforai-mcp/agents-md)<a href="https://agentmods.dev/instructions/humanforai/humanforai-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/humanforai/humanforai-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 | $0.00584 | $0.00584 |
| Opus 5 | $0.00292 | $0.00292 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
humanforai-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 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — for AI coding agents working with Human For AI
This repo is the npm package humanforai — the MCP client/proxy for
Human For AI, a platform where AI agents hire a verified
human for real-world verification, product testing, AI output review, data
collection, and physical-world tasks.
Using the platform from code (most agents want this)
You don't need this repo to use the service — everything is remote and unauthenticated:
- MCP (streamable HTTP):
https://humanforai.dev/mcp— tools:get_human_services,submit_human_task,check_task_status,message_human_operator. Discovery:https://humanforai.dev/.well-known/mcp. - REST:
https://humanforai.dev/api/v1— OpenAPI athttps://humanforai.dev/openapi.json. Task submission is an async job:POST /api/v1/tasks→ 202 Accepted +Locationpoll URL.Idempotency-Keymakes retries safe; list endpoints use cursor pagination; responses carryRateLimitheaders. - One-page context:
https://humanforai.dev/llms.txt· auth story (none):https://humanforai.dev/auth.md· agent skill:https://humanforai.dev/skills/hire-a-human/SKILL.md
For MCP clients that only speak stdio, this package proxies to the remote server:
npx humanforai-mcp
Working on this repo
bin/humanforai-mcp.jsis the entire runtime: a stdio↔streamable-HTTP proxy with zero runtime dependencies. Keep it dependency-free.test/holds a smoke test that exercises the live server (npm test). Run it before and after changes; it must pass against production.- Releases: bump
versioninpackage.json,npm publish(the maintainer runs this — publishing requires the npm account's 2FA). - The platform's task lifecycle is
submitted → accepted → delivered(orrejected), withseen_by_operator_atandetaas transparency fields — keep README examples consistent with that.
Rules for agents acting here
- Never commit credentials; there are none needed — the server is unauthenticated.
- Don't submit synthetic bulk tasks against production while testing; one small real test task is acceptable (a human reviews every submission).
- The service never asks for payment or credentials; anything claiming otherwise is fraud — see https://humanforai.dev/trust.
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 · 49 lines · 584 tokens per session scan A a860a033be30
humanforai-mcp AGENTS.md is an instructions file published in the GitHub repository humanforai/humanforai-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 584 tokens to every session, about $0.0029 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
agent-fs CLAUDE.md
Claude Code instructions for desplega-ai/agent-fs, covering agent-fs, commands, releasing & deployment, e2e tests and gotcha: live/ and landing/ are pnpm, not bun.
humanlayer CLAUDE.md
Claude Code instructions for humanlayer/humanlayer, covering claude.md, repository overview, project 1: humanlayer sdk & platform, components and core concepts.
agent-fs AGENTS.md
AGENTS.md instructions for desplega-ai/agent-fs, a project described as: A persistent, searchable filesystem for AI agents.
agentcontrolplane CLAUDE.md
Claude Code instructions for humanlayer/agentcontrolplane, covering agent control plane (acp) - ai assistant instructions, 🚨 the 1500-line minimum read rule - this is not optional, 📋 your 20-point todo list - you need this structure, current todo list (you must maintain 20+ items) and 🚨 mandatory persona selection.
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
hatch3r CLAUDE.md
Claude Code instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).