Governance-first agent command center for workflow automation, validation, policy, documentation sync, and execution discipline.
This repository also configures its own agents. See what agent-command-center tells them →
Skill Claude CodeCodex
Use for periodically reviewing which skills are overused, underused, missing, or creating friction by examining recent governance artifacts, handoffs, instruction trackers, and task outcomes.
Skill Claude CodeCodex
Use only when the user explicitly asks to rate, score, grade, benchmark, or assign a numeric or weighted quality rating. Do not activate for a plain review, audit, assessment, evaluation, comparison, critique, or feedback request unless the user also requests scoring or a formal rubric.
Skill Claude CodeCodex
Model end-user goals, expected baseline behavior, and product tradeoffs when a feature request requires product judgment. Use for feature planning or authorized implementation with meaningful user-experience choices; do not use for fixed mechanical work, and never treat a plausible enhancement as authorized scope.
Skill Claude CodeCodex
Use when the user explicitly requests shorter or lower-token output, or when long context is causing concrete retrieval or response overhead. Limit this skill to context selection and output efficiency; do not activate it for routine tasks, project intake, testing ownership, deployment policy, or repository…
Skill Claude CodeCodex
Use for building or reviewing UI design quality using principles synthesized from trusted UX sources (Apple HIG, Google Material, MIT HCI, Nielsen heuristics, WCAG).
Skill Claude CodeCodex
Use only when the user explicitly requests the Spatial Canvas design system or when repository evidence establishes Spatial Canvas as the existing interface architecture being modified. Do not activate for generic frontend, UI, UX, layout, navigation, interaction, or visual-system work.
Skill Claude CodeCodex
Use only when the user explicitly asks to record or audit instructions, when a durable cross-task directive changes in a repository that already opts into tracking, or when maintaining an existing instruction ledger is the requested work. Do not activate for ordinary task requests, transient acceptance criteria…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: