Documentation

Install skills

Node.js 22.14 or newer is required for the installer lane. The installer detects a harness, or accepts an explicit target, and writes each skill as a direct child of that root. It reports the root it wrote and exits nonzero when a target is incomplete.

npx --yes --package @youcisla/agent-foundry agent-foundry-install

node scripts/install.js --list

node scripts/install.js --harness=codex --dry-run

Run the installer from the repository clone. The npm package exposes the same installer as the agent-foundry-install binary.

Install the runtime (optional)

The runtime is a Python package (Python 3.10 to 3.14). It provides the CLI, the local daemon, the SQLite execution log, and the MCP stdio server. The distribution contains no skill content; install the corpus with the installer above.

pip install agent-foundry-runtime

uvx agent-foundry-runtime mcp

Provider configuration is local. Set the key your model configuration expects in the environment or config file; agent-foundry doctor reports whether a key is present without printing it.

Verify discovery

For skills-only use, confirm that the harness root contains one directory per skill:

ls ~/.claude/skills | head

For the runtime, the doctor command checks configuration, the index, the daemon, and the provider key. A failure exits nonzero so it can gate a setup script.

agent-foundry doctor

agent-foundry index

MCP server

The MCP server speaks JSON-RPC over stdio and exposes the same catalog operations as the CLI: list and search skills, get one skill, plan, execute, verify, classify an action, read runtime status, and read execution history.

{
  "mcpServers": {
    "agent-foundry": {
      "command": "uvx",
      "args": ["agent-foundry-runtime", "mcp"]
    }
  }
}

MCP clients start the server themselves; no daemon port has to be open.

Local daemon

agent-foundry serve starts a FastAPI daemon on 127.0.0.1:8765. Most CLI commands start it lazily when needed. Requests need a bearer token stored in a user-owned file, and the daemon refuses non-loopback binding unless explicitly configured.

agent-foundry serve

curl -s http://127.0.0.1:8765/health

Configuration and retention

Configuration lives in ~/.config/agent-foundry/config.toml (platform-aware). Executions are stored in a local SQLite database. Content retention can be disabled; pruning is explicit and supports a dry run.

agent-foundry init

agent-foundry prune --dry-run

Security boundary

• The daemon binds loopback, requires a bearer token for requests, and rejects unexpected Host and Origin headers.
• Provider keys are read from your environment or config and are never printed by doctor.
• Policy checks can classify a shell, file, text, or network action as allow, confirm, or deny before it runs.
• The public site has no telemetry and no third-party runtime JavaScript.

Troubleshooting