grok-faf-mcp: Instructions file for Codex

AGENTS.md

grok-faf-mcp AGENTS.md is an instructions file for Codex, OpenCode from Wolfe-Jam/grok-faf-mcp. It costs 566 tokens per session, scanned A, original, MIT.

Project instructions for grok-faf-mcp, a TypeScript MCP service that gives xAI Grok persistent project context. MCP is a standard for connecting AI systems to external tools and services.

In plain words
What is it for?
Use them when developing, deploying, or maintaining grok-faf-mcp, including its Node.js, Cloudflare Workers, TypeScript, MCP, and GitHub Actions setup.
Why use it?
They provide the project's context, technology choices, deployment locations, compatibility details, and current version information so work follows the repository's intended design.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is Wolfe-Jam/grok-faf-mcp's own configuration. It tells Codex and OpenCode how to work on grok-faf-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything grok-faf-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Wolfe-Jam/grok-faf-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.

Copy the file
curl -O https://raw.githubusercontent.com/Wolfe-Jam/grok-faf-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Wolfe-Jam/grok-faf-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for grok-faf-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/wolfe-jam/grok-faf-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/wolfe-jam/grok-faf-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/wolfe-jam/grok-faf-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wolfe-jam/grok-faf-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.

agentmods 80×15 button for grok-faf-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wolfe-jam/grok-faf-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wolfe-jam/grok-faf-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 566 This file is loaded in full into every session.
When invoked 566 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00566 $0.00566
Opus 5 $0.00283 $0.00283
Sonnet 5 $0.00113 $0.00113
Haiku 4.5 $0.00057 $0.00057

Measured 9d ago against content hash d7117d7b6752, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

grok-faf-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 9d 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.

AGENTS.md · 31 lines

What it actually says

AGENTS.md — grok-faf-mcp

Auto-generated from project.faf — do not edit directly

Project Context

  • Name: grok-faf-mcp
  • Goal: Persistent project context for xAI Grok. First MCP for Grok • First FAF MCP online • MCPaaS pattern origin. IANA-registered .faf + .fafm. Grok asked for MCP on a URL — this is it.
  • Language: TypeScript

Stack

  • backend: MCP SDK (TS)
  • api_type: MCP (stdio + Streamable HTTP)
  • runtime: Node.js
  • hosting: Cloudflare Workers
  • build: TypeScript (tsc)
  • cicd: GitHub Actions

Human Context

  • who: Developers using xAI Grok with MCP
  • what: First MCP for Grok — also first FAF MCP online. Persistent AI context via IANA-registered .faf + .fafm.
  • why: Every AI session starts from zero. grok-faf-mcp gives Grok persistent project DNA.
  • where: npm registry, Cloudflare Workers (mcpaas.live/grok/mcp/v1), MCP Registry (one.faf/grok-faf-mcp)
  • when: Shipped 2026-08-20 — current v1.10.0 The No-Fluff Edition (no fluff in a project.faf; faf_enhance gone; RAG default grok-4.6). v1.9.1 registry display title Grok FAF, emitter-sourced via faf server-card. v1.9.0 The ZEPH Default Edition (ZEPH default-ON). v1.8.1 patch: symmetric .fafm refresh receipts. v1.8.0 The Closed-Loop Edition; v1.7.0 The Grounded Memory Edition; v1.6.0 ZEPH Edition; v1.5.5 Glama Core-tier.
  • how: bunx grok-faf-mcp (local stdio) or hosted on Cloudflare Workers (mcpaas.live/grok/mcp/v1) — 12 core tools by default (extended set behind FAF_TOOLS=all), Streamable HTTP transport, Mk4 WASM scoring kernel
Changes

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.

  1. 9d ago First seen · 31 lines · 566 tokens per session scan A d7117d7b6752

Subscribe to this mod's changes

grok-faf-mcp AGENTS.md is an instructions file published in the GitHub repository Wolfe-Jam/grok-faf-mcp (18 stars, last pushed yesterday), licensed MIT. It adds 566 tokens to every session, about $0.0028 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens