Tools & Skills

1. Skills Live

Reusable instruction sets that agents (e.g. in Cursor, Claude Projects) can load to apply AAF when designing or reviewing agentic systems. Copy a skill into your project or reference it from the repo.

• Architecture Review aaf-architecture-review — Pillar checklist, design-time spec and pre-production review.
• Security aaf-security — Boundaries, tool actuation, epistemic gatekeeping, supply chain.
• Epistemic Gates aaf-epistemic-gates — When and where to place validation and authority gates.
• Cost & Context aaf-cost-context — Budgets, model routing, token economics, context discipline.
• Cross-Cutting Foundations aaf-cross-cutting — Context optimization and autonomy & outcome governance.
• ACC Implementation aaf-acc-implementation — Agent Control Contract template, placement, and usage.
• Orchestration & OCC aaf-orchestration-occ — Orchestrator Capability Contract and multi-agent governance.

Skills live in tools/skills/ on GitHub.

2. MCP Server Live

A Model Context Protocol server that exposes the framework as tools. AI assistants that support MCP can call these tools to get accurate, framework-grounded answers.

• aaf_lookupCore — Search the framework docs for a term or topic.
• aaf_checklistCore — Architecture review checklist (pre-production readiness).
• aaf_pillars_summaryCore — Summary of the six pillars and cross-cutting foundations.
• aaf_get_skillCore — Retrieve the full content of any skill by ID.
• aaf_design_questionsDesign — Design questionnaire for a given autonomy level.
• aaf_tradeoff_analysisDesign — Deterministic trade-off analysis from design choices.
• aaf_generate_accDesign — Generate an Agent Control Contract from design answers.
• aaf_scaffold_specBuild — File manifest for agent code scaffold generation.
• aaf_posture_interpretReview — Interpret posture report with trade-off tensions.
• aaf_review_against_accReview — Gap analysis: ACC vs actual implementation.
• aaf_pillar_guidanceCross-cutting — Targeted design guidance for a specific pillar.
• aaf_security_scanSecurity — CIA-aligned security scan with actionable recommendations.

Using the MCP server in different IDEs

The hosted AAF server speaks HTTP (Streamable MCP). Editors differ in how they connect:

• Direct URL — Some clients let you register the server by URL only (no local process). Fastest when supported.
• Local bridge (mcp-remote) — Many IDEs only launch stdio MCP servers. Use npx mcp-remote … so the editor talks to localhost while the bridge forwards to agenticaf.io. Requires Node.js 18+.

Option A — Direct URL (Cursor and clients that support remote HTTP MCP):

{
  "mcpServers": {
    "aaf": {
      "url": "https://www.agenticaf.io/api/mcp"
    }
  }
}

Option B — mcp-remote bridge (Antigravity, Claude Desktop, Windsurf, and any stdio-only MCP host). Merge under mcpServers:

{
  "mcpServers": {
    "aaf": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.agenticaf.io/api/mcp",
        "--transport",
        "http-first"
      ]
    }
  }
}

After saving, restart the app or reload MCP. Ask the assistant what tools it has — you should see aaf_lookup, aaf_checklist, etc. If the deployment requires an API key, add --header Authorization:${AAF_MCP_AUTHORIZATION} and set AAF_MCP_AUTHORIZATION to Bearer <key> in env — see api/README.md.

Note: Some clients rename the server (e.g. user-aaf). That is normal. Windsurf MCP availability may depend on your plan — check Codeium’s docs.

3. AAF Posture Report Live

A CLI that scans a codebase and produces an AAF posture report: how well the project aligns with the eight pillars. Output is human-readable HTML/markdown and optional JSON for CI.

CLI lives in tools/aaf-posture/ on GitHub.