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/acedatacloud/facetransformmcp/claude-mdgit clone --depth 1 https://github.com/AceDataCloud/FaceTransformMCPWrote 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/acedatacloud/facetransformmcp/claude-md)<a href="https://agentmods.dev/instructions/acedatacloud/facetransformmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/acedatacloud/facetransformmcp/claude-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.00521 | $0.00521 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
FaceTransformMCP CLAUDE.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.
What it actually says
FaceTransformMCP
MCP (Model Context Protocol) server for the AceDataCloud Face Transform API — seven face tools covering keypoint detection, beautification, age/gender transform, face swap, cartoonization, and liveness detection.
Project Structure
core/
config.py — Settings dataclass (API token, base URL, timeouts)
server.py — FastMCP server singleton + optional OAuth provider
client.py — FaceClient: async httpx wrapper for /face/* endpoints
types.py — Literal types (FaceAnalyzeMode, FaceModelVersion, ...)
exceptions.py — Error classes (FaceAuthError, FaceAPIError, FaceTimeoutError)
oauth.py — Generic AceDataCloud OAuth 2.1 provider (PKCE)
utils.py — Shared response helpers (kept from template; unused by face)
tools/
face_tools.py — All seven face tools + face_get_usage_guide
prompts/
__init__.py — face_guide, face_workflow_examples
tests/
test_smoke.py — Smoke tests (settings, server import, tool registration)
Adding / updating a face endpoint
- Source of truth — the upstream OpenAPI spec lives at
https://docs.acedata.cloud/openapi/face.json(or the matching file in theDocs/submodule). - Update client — add a method to
FaceClientincore/client.py. - Add tool — register a new
@mcp.tool()function intools/face_tools.py. - Update prompts — extend
face_guideandface_workflow_examples. - Update server card — append the tool description to the
server_cardpayload inmain.py. - Update README + CHANGELOG.
- Add tests — at minimum a smoke test that the tool is registered.
- Run
ruff check .andpytest --cov=core --cov=toolsbefore opening a PR.
Development
pip install -e ".[dev,test]"
pytest --cov=core --cov=tools
ruff check .
Local run
cp .env.example .env
# fill in ACEDATACLOUD_API_TOKEN
python main.py # stdio
python main.py --transport http # HTTP on :8000
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 · 57 lines · 521 tokens per session scan A ee4e7e6cc653
FaceTransformMCP CLAUDE.md is an instructions file published in the GitHub repository AceDataCloud/FaceTransformMCP (0 stars, last pushed 12d ago), licensed MIT. It adds 521 tokens to every session, about $0.0026 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
ditherer AGENTS.md
Instructions for gyng/ditherer, covering ditherer — agent guidelines, project overview, architecture, component hierarchy (atomic design) and state management.
obsidian-transcriber AGENTS.md
Instructions for dsebastien/obsidian-transcriber, covering project documentation, documentation surfaces, project overview, agent workflow and session-start checklist.
ApraPipes CLAUDE.md
Claude Code instructions for Apra-Labs/ApraPipes, covering claude.md - aprapipes declarative pipeline, current phase: sprint 12 - windows integration test fix, sdk structure (complete), critical rules and 1. build and test before commit (mandatory).
CShade AGENTS.md
Instructions for papadanku/CShade, covering cshade agent instructions, repo type, structure, file types and coding conventions (from readme.md).
ditherer CLAUDE.md
Instructions for gyng/ditherer, covering ditherer and quick reference.
imagesorcery-mcp GEMINI.md
Instructions for sunriseapps/imagesorcery-mcp: On each new session, please re-read the README.md file to ensure you have the most up-to-date project context and instructions.