burhan-mop
v0.1.8
Published
MOP portable agent memory core installer and CLI.
Maintainers
Readme
What Is BURHAN-MOP?
BURHAN-MOP is a portable MOP (Memory of Planet) core for AI coding workspaces. It gives every supported AI provider the same project memory, agent rules, workflow gates, artifact folders, autosycn flow, and deployment setup.
The goal is simple: install once, then Claude, Codex / ChatGPT, Gemini, and Antigravity can enter the same project with the same source of truth.
Install
Run this inside the project root:
npx burhan-mop install
npx burhan-mop doctorInstall into another folder:
npx burhan-mop install --target "C:\path\to\project"Overwrite an existing MOP install:
npx burhan-mop install --forceThe installer shows a clean terminal UI by default. For automation, use JSON:
npx burhan-mop install --json
npx burhan-mop doctor --jsonAfter install, open your AI coding chat in that project and run:
/mop-setupWhat Gets Installed
| Path | Purpose |
| --- | --- |
| .MOP/ | MOP state, protocol, scripts, workflow config, and artifact templates. |
| AGENTS.md | Provider-neutral instructions for Codex / ChatGPT coding agents. |
| CLAUDE.md | Claude Code entrypoint and behavior rules. |
| GEMINI.md | Gemini CLI entrypoint. |
| .agents/ | Antigravity-compatible agents and skills. |
| .codex/, .gemini/, .claude/ | Provider-specific config and skill surfaces. |
Core Features
| Feature | What it does |
| --- | --- |
| Auth Gate | First action is always setup/login. No work starts before the gate passes. |
| Agent Router | Picks one primary agent and adds support agents only when useful. |
| Party Mode | Shows visible agent-to-agent discussion for multi-role decisions. |
| MOP Workflow | BMAD-inspired flow from idea to release with readiness checks. |
| Artifacts | Keeps plans, specs, reviews, and release notes under .MOP/artifacts/. |
| Autosycn | Commits and pushes as the real user, not as the AI tool identity. |
| Auto Deploy | Optional setup path for GitHub, Docker, and Vercel. |
First Session Flow
1. AI reads .MOP/STATE.json
2. If not initialized, AI asks you to run /mop-setup
3. Setup asks for project name, owner, codename, password, mode, language, and GitHub info
4. After login, every task goes through the Agent Router
5. Complex tasks use MOP Workflow and readiness gates before codingUseful Commands
npx burhan-mop install
npx burhan-mop doctor
npx burhan-mop packageLocal project helpers:
node .MOP/scripts/mop-core.mjs status
node .MOP/scripts/mop-core.mjs validate
node .MOP/scripts/mop-workflow.mjs help --actor <codename> --task "<task>"
node .MOP/scripts/mop-autosycn.mjs run --actor <codename> --reason "<what changed>"Team Workflow
In team mode, work is pushed to a user branch first:
dev/<codename> -> BURHAN-MOP review -> mainBURHAN-MOP acts as the merge guardian. It checks the branch, validates state, and merges only when the workflow is safe.
Release
| Item | Value |
| --- | --- |
| npm package | burhan-mop |
| latest command | npx burhan-mop install |
| GitHub release | v0.1.8 |
| Node | >=20 |
Links
- npm: https://www.npmjs.com/package/burhan-mop
- GitHub: https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP
- Bahasa Melayu README: README.bm.md
