cardinal
v0.29.4Connect Claude Code to Cardinal: telemetry to the Outcomes Dashboard + unified Cardinal MCP tools, with a per-turn git_state hook that derives initiative name and type from the current branch so the Outcomes Dashboard can map sessions to repos/branches/PRs/initiatives.
By CardinalHQLicense: Apache-2.00 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 7 skill or MCP entries
- Source updated
- Aug 28, 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 plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install cardinal@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
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/cardinalhq/cardinal-claude-pluginClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/cardinal/.
Plugin files
├── .claude-plugin/plugin.json├── skills/connect/SKILL.md├── skills/deploy-sentinel/SKILL.md├── skills/disconnect/SKILL.md├── skills/install-site/SKILL.md├── skills/mechanize/SKILL.md├── skills/optimize-toolkit/SKILL.md└── skills/status/SKILL.md
Included Skills7
Connect Claude Code to Cardinal — runs the device-code flow to enable telemetry to the Outcomes Dashboard AND the unified Cardinal MCP tools, in one consent.
Author a Sentinel Custom Resource next to a compiled Sentinel directory and guide the user through the git-push → ArgoCD → controller reconciliation flow.
Disconnect this Claude Code install from Cardinal — revoke the MCP key, strip the plugin's env block, delete local state.
Install a Cardinal site (perch + optional POC Lakerunner) into a Kubernetes cluster you have access to, driven by the Cardinal control-plane API.
Compile a completed Claude Code session (a past investigation) into a candidate Sentinel DAG plus rationale — a reusable procedure that could later be executed against a similar problem. Use when the user asks to /mechanize, compile a session, or extract a reusable investigation procedure. Compiles, then trial-executes the DAG against captured fixtures and checks it reaches the same conclusion the investigation did before emitting.
Mine this engineer's own session telemetry for capability-fit recommendations across agents, skills, commands, and MCP tools (extract a new sub-agent or command, pin/downgrade a model tier, adopt or swap an existing capability, consolidate duplicates) and, on confirmation, write the accepted artifact into the working tree.
Verify the Cardinal plugin's wiring on this Claude Code install (telemetry and/or MCP).
Plugin manifests1
{
"name": "cardinal",
"version": "0.29.4",
"description": "Connect Claude Code to Cardinal: telemetry to the Outcomes Dashboard + unified Cardinal MCP tools, with a per-turn git_state hook that derives initiative name and type from the current branch so the Outcomes Dashboard can map sessions to repos/branches/PRs/initiatives.",
"author": {
"name": "CardinalHQ",
"url": "https://cardinalhq.io"
},
"homepage": "https://github.com/cardinalhq/cardinal-claude-plugin",
"license": "Apache-2.0"
}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.
[cardinal on Agent Plugins Marketplace](https://pluginsmp.com/plugins/cardinal)