agent-implant

MCP plugin for Claude Code (and, eventually, other agent platforms) that runs inside an AI agent to:

1. Register the agent against an Agent University invite link.
2. Scan the workspace for legible context (CLAUDE.md, memory/, .cursorrules, etc).
3. Submit a worldmodel back to agents-university-platform so the owner can inspect what their agent believes.

Status

Phase 3B scaffold. The repo carries the public contract with the backend (Zod schemas), an API client, an identity/storage layer, an MCP server stub, and a workspace scanner stub. Orchestrator logic (the P1-P9 chat beats defined in the MVP1 spec) and real extraction logic are follow-ups.

Architecture

agent-implant/
├── manifest.json                 Claude Code plugin manifest
├── src/
│   ├── cli.ts                    npx entry (install / diagnose)
│   ├── server.ts                 MCP server; registers tools
│   ├── lib/
│   │   ├── contracts.ts          Zod schemas mirroring /api/plugin/* endpoints
│   │   ├── api-client.ts         typed fetch with bearer agent_key
│   │   ├── identity.ts           install_id generation + persistence
│   │   ├── storage.ts            ~/.agent-university/ state file
│   │   └── scanner.ts            workspace file discovery
│   └── orchestrator/
│       └── beats.ts              P1-P9 chat-beat state machine (stub)
├── test/
└── .github/workflows/ci.yml

Contract with the backend

Authoritative spec lives in agents-university-twin/product/features/MVP1/api-endpoints.md. The Zod schemas in src/lib/contracts.ts are the plugin-side mirror. If the backend contract changes, contracts.ts updates in the same PR.

Identity

install_id is a UUID v4 generated on first run and persisted to ~/.agent-university/identity.json. agent_key is issued by the backend at registration time and stored in the same file (chmod 600). The file never leaves the user's machine.

Development

npm install
npm run typecheck
npm run test
npm run build      # emits dist/

License

TBD.