agentmods.dev

run

run is a command for Claude Code from ANcpLua/ancplua-claude-plugins. It costs 9 tokens per session (507 once invoked), scanned A, original, MIT.

A command that advances the next ready stage of the Elegance Pipeline by creating the required specialist agent and submitting its result to shared workflow state. The pipeline is a staged process for assessing and improving code quality.

In plain words
What is it for?
Use it to run scouts, judges, planners, verifiers, or the gated implementer after checking the pipeline status.
Why use it?
It coordinates dependent tasks without requiring you to manually decide which agent should run next.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the elegance-pipeline plugin — 1 skill, 3 commands, 6 agents shipped together

not rated 6repo 2d ago A scan 9 tokens original MIT

Good fit Use it to run scouts, judges, planners, verifiers, or the gated implementer after checking the pipeline status.

Compare 6 commands from other repositories ↓
View source ↗ ANcpLua/ancplua-claude-plugins
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ANcpLua/ancplua-claude-plugins
Claude Code
/plugin install elegance-pipeline

Made for: Claude Code.

Or install elegance-pipeline, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 6 agents.

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 run

README.md
[![agentmods](https://agentmods.dev/badge/commands/ancplua/ancplua-claude-plugins/run/github.svg)](https://agentmods.dev/commands/ancplua/ancplua-claude-plugins/run)
Your own site
<a href="https://agentmods.dev/commands/ancplua/ancplua-claude-plugins/run"><img src="https://agentmods.dev/badge/commands/ancplua/ancplua-claude-plugins/run/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 run

Your own site · 80×15
<a href="https://agentmods.dev/commands/ancplua/ancplua-claude-plugins/run"><img src="https://agentmods.dev/badge/commands/ancplua/ancplua-claude-plugins/run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 507 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.00009 $0.00507
Opus 5.5 $0.00004 $0.00203
Sonnet 5.5 $0.00002 $0.00101
Haiku 4.5 $0.00001 $0.00051

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

Security

Grade A, and why

run 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 1mo 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.

plugins/elegance-pipeline/commands/run.md · 57 lines

What it actually says

Run the next ready stage of the elegance pipeline.

Procedure

  1. Check status:
python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] status
  1. For each ready slot, render the prompt:
python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] prompt --role <role> --slot <slot>

  1. Spawn the matching subagent with the rendered prompt as the task:

    • scout-* slots -> spawn elegance-pipeline:elegance-scout (or the exact fully qualified runtime ID if it differs)
    • judge-* slots -> spawn elegance-pipeline:elegance-judge (or the exact fully qualified runtime ID if it differs)
    • planner-1 -> spawn elegance-pipeline:elegance-planner
    • verifier-1 -> spawn elegance-pipeline:elegance-verifier
    • implementer-1 -> spawn elegance-pipeline:elegance-implementer

  2. After each agent completes, pipe its result to the state manager:

echo "<agent output>" | python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] submit \
  --role <role> --slot <slot> --stdin

  1. Check status again and repeat for newly unlocked slots.

  2. Stop when no more slots are ready or the pipeline is complete.

Arguments

Pass $ARGUMENTS to control which stage to run:

  • scouts — run only scout phase
  • judges — run only judge phase
  • all — run all phases sequentially (default)
  • A specific slot like scout-1 or judge-2

Rules

  • Never bypass stage gates
  • Run scouts and judges in parallel (background agents)
  • Run planner, verifier, implementer sequentially (foreground)
  • If the verifier says no implementation is warranted, report that and stop
  • Use a distinct --state-dir for each spec if you want dedicated teams in parallel
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. 1mo ago First seen · 57 lines · 9 tokens per session scan A b93fcdb77bbc

Subscribe to this mod's changes

run is a command published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 507 once invoked, about $0.0000 per session on Opus 5.5. 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-10-01.

Building agentsProject managementancplua-fleet
Related

run compared with commands from other repositories

run next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
runANcpLua/ancplua-claude-pluginsCommand62d agoMITA9Claude Code
checklistgithub/spec-kitCommand149ktodayMITA13Claude Code
clarifygithub/spec-kitCommand149ktodayMITA27Claude Code
specifygithub/spec-kitCommand149ktodayMITA13Claude Code
convergegithub/spec-kitCommand149ktodayMITA35Claude Code
implementgithub/spec-kitCommand149ktodayMITA14Claude Code
speckit.bug.fixgithub/spec-kitCommand149ktodayMITA12Claude Code