agentmods.dev

astrodeck: Command for Claude Code

.claude/commands/plenum.md

plenum is a command for Claude Code from holger1411/astrodeck. It costs 0 tokens per session (1,018 once invoked), scanned A, original, MIT.

A command that coordinates several specialist review agents to inspect an AstroDeck project and combine their findings into one review.

In plain words
What is it for?
Use it to review a whole project, page, component, code change, or performance problem, with reviewers selected for the chosen scope.
Why use it?
It brings design, accessibility, usability, code, search visibility, and performance checks together instead of requiring separate reviews.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions AGENTS.md.

This is holger1411/astrodeck's own configuration. It tells Claude Code how to work on astrodeck itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything astrodeck configures →

not rated 81repo +1 2mo ago A scan 0 tokens original MIT
View source ↗ holger1411/astrodeck astrodeck.dev
Reuse

Borrowing it

Nothing to install: this file belongs to holger1411/astrodeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/holger1411/astrodeck/main/.claude/commands/plenum.md
Clone the repo
git clone --depth 1 https://github.com/holger1411/astrodeck

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plenum

README.md
[![agentmods](https://agentmods.dev/badge/commands/holger1411/astrodeck/plenum/github.svg)](https://agentmods.dev/commands/holger1411/astrodeck/plenum)
Your own site
<a href="https://agentmods.dev/commands/holger1411/astrodeck/plenum"><img src="https://agentmods.dev/badge/commands/holger1411/astrodeck/plenum/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plenum

Your own site · 80×15
<a href="https://agentmods.dev/commands/holger1411/astrodeck/plenum"><img src="https://agentmods.dev/badge/commands/holger1411/astrodeck/plenum.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,018 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01018
Opus 5.5 $0.00000 $0.00407
Sonnet 5.5 $0.00000 $0.00204
Haiku 4.5 $0.00000 $0.00102

Measured 2mo ago against content hash 3af4af41b712, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plenum scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/plenum.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plenum: Multi-Agent Review Orchestrator

You are the Plenum orchestrator. Your job is to coordinate multiple specialist review agents to produce a comprehensive, consolidated review of the AstroDeck project.

Scope requested by the user: $ARGUMENTS

Step 1: Clarify Scope

If the scope above is empty, ask the user what they want reviewed. Options:

  • Whole project — full review of all pages and components
  • Specific page — e.g., "review the pricing page"
  • Component — e.g., "review the Hero component"
  • Git diff — review only what changed since last commit (run git diff to get the scope)
  • Performance issue — focused performance investigation
  • Explicit "all" — all 6 agents regardless of scope

If the user already specified the scope in their message, skip the question and proceed.

Step 2: Select Agents Based on Scope

Choose agents automatically based on what is being reviewed:

Scope Agents
CSS/style changes design-review, a11y-review, code-review
New page ALL 6 agents
Content changes seo-review, a11y-review
Component design-review, ux-review, a11y-review, code-review
Performance issue perf-review, code-review
Explicit "all" ALL 6 agents
Whole project ALL 6 agents

Step 3: Spawn Agents in Parallel

For each selected agent, use the Agent tool to spawn a subagent. Pass each agent:

  1. The agent definition file path (e.g., .claude/agents/design-review.md)
  2. The review scope (which files/pages/components to examine)
  3. A list of the specific files relevant to the scope

Spawn all selected agents in parallel — do not wait for one to finish before starting another.

Each agent will:

  • Read AGENTS.md for project conventions
  • Read its specific globals files
  • Analyze the scope
  • Return findings in the standard format (Critical / Important / Nice-to-have / Positive)

Step 4: Consolidate Results

Once all agents have reported back, produce a consolidated report:

4a: Identify Overlaps

When multiple agents flag the same issue, merge them into a single finding and note which disciplines identified it. This strengthens the case for fixing it.

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 127 lines · 0 tokens per session scan A 3af4af41b712

Subscribe to this mod's changes

plenum is a command published in the GitHub repository holger1411/astrodeck (81 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,018 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agentsCode review
Related

plenum compared with commands from other repositories

plenum next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
plenumholger1411/astrodeckCommand812mo agoMITA0Claude Code
diff-reviewcoco-research/cocoCommand785yesterdayApache-2.0A11Claude Code
review-branchdamusix/atomic-claudeCommand1154d agoMITA35Claude Code
refactorRchGrav/claudeboxCommand1.2k1mo agoMITA9Claude Code
spec-trace-requirementsrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
initazrtydxb/procoderCommand21111d agoApache-2.0A16Claude Code