Agent Plugins Marketplace
← All plugins

archcore

v0.10.3

Spec-driven development and context engineering for AI coding agents, backed by project context in Git.

Codex2 Skills1 MCP serverstdio

By ArchcoreLicense: Apache-2.01.1k GitHub starsUpdated 11 hours ago

Directory evidence

Runtimes
Codex
Parsed components
3 skill or MCP entries
Source updated
Sep 23, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install archcore for Codex

Installs for the current user
codex plugin marketplace add hashgraph-online/awesome-codex-plugins
codex plugin marketplace upgrade awesome-codex-plugins
codex plugin add archcore@awesome-codex-plugins

Paste and run these commands in a terminal with Codex. They add and refresh the awesome-codex-plugins catalog, then install this plugin.

Compatibility: the page URL and API slug “archcore-2” remain stable.

  • Codex: archcore-2@agent-plugin-marketplace → archcore@awesome-codex-plugins

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/hashgraph-online/awesome-codex-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/archcore-ai/archcore/.

Plugin files

plugins/archcore-ai/archcore/
├── .codex-plugin/plugin.json
├── skills/document/SKILL.md
├── skills/review/SKILL.md
└── .mcp.json

Included Skills2

documentskills/document/SKILL.md

Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.

reviewskills/review/SKILL.md

The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.

MCP servers1

archcorestdio
command
archcore
args
mcp

Plugin manifests1

plugins/archcore-ai/archcore/.codex-plugin/plugin.json
{
  "name": "archcore",
  "description": "Spec-driven development and context engineering for AI coding agents, backed by project context in Git.",
  "version": "0.10.3",
  "author": {
    "name": "Archcore",
    "url": "https://archcore.ai"
  },
  "license": "Apache-2.0",
  "homepage": "https://archcore.ai/plugin",
  "repository": "https://github.com/archcore-ai/archcore",
  "keywords": [
    "codex",
    "codex-cli",
    "agents-md",
    "mcp",
    "ai-agents",
    "ai-coding",
    "coding-agents",
    "project-context",
    "context",
    "context-engineering",
    "architecture",
    "adr",
    "knowledge-management",
    "rules",
    "decisions",
    "conventions",
    "git-native",
    "skills",
    "subagents",
    "spec-driven-development",
    "documentation",
    "specs"
  ],
  "skills": "./skills/",
  "hooks": "./hooks/codex.hooks.json",
  "mcpServers": "./.codex.mcp.json",
  "interface": {
    "displayName": "Archcore",
    "shortDescription": "Spec-driven development and context engineering for AI coding agents.",
    "longDescription": "Archcore brings spec-driven development and automatic project context to Codex. Specs, architecture, decisions, rules, and plans live in Git and are applied as the agent works.",
    "developerName": "Archcore",
    "category": "Productivity",
    "capabilities": [
      "Read",
      "Write"
    ],
    "websiteURL": "https://archcore.ai",
    "privacyPolicyURL": "https://archcore.ai/privacy",
    "termsOfServiceURL": "https://github.com/archcore-ai/archcore/blob/main/docs/TERMS.md",
    "defaultPrompt": [
      "Use Archcore to review this work against project decisions",
      "Use Archcore to plan this change",
      "Use Archcore to check whether source edits need doc updates"
    ],
    "brandColor": "#2563EB",
    "composerIcon": "./assets/icon.png",
    "logo": "./assets/logo.png",
    "screenshots": []
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[archcore on Agent Plugins Marketplace](https://pluginsmp.com/plugins/archcore-2)