demo

demo is a command for coding agents from ccplugins/awesome-claude-code-plugins. It costs 22 tokens per session (1,019 once invoked), scanned C, original, Apache-2.0.

A guided demonstration that creates a temporary Git repository, adds known bugs, and has Claude and Codex review the code independently. It shows which model finds each bug without changing your files.

In plain words
What is it for?
Use it to try cross-model code review and compare what Claude and Codex notice in deliberately flawed code.
Why use it?
It gives you a safe, quick way to see how the two-model review process works before using it on a real project.

Command

Part of the claudex plugin — 1 skill, 6 commands shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/ccplugins/awesome-claude-code-plugins/demo
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins

Or install claudex, the plugin that ships this one along with the rest of its 1 skill, 6 commands.

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 demo

README.md
[![agentmods](https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/demo.svg)](https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/demo)
Your own site
<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/demo"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/demo.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 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,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00022 $0.01019
Opus 5 $0.00011 $0.00509
Sonnet 5 $0.00004 $0.00204
Haiku 4.5 $0.00002 $0.00102

Measured yesterday against content hash 3a04bf1c1930, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

demo scanned grade C with 1 finding 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 yesterday.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

8. **Clean up.** Remove the throwaway directory (`rm -rf "$DEMO"` — it is a
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • demo — 100% identical, 0 lines differ
plugins/claudex/commands/demo.md · 93 lines

How it starts

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

You are running the ClauDex demo — a safe, self-contained first experience of the duet. You will plant bugs, let both models review them independently, and reveal who caught what. Everything happens in a throwaway directory; the user's own files are never touched.

Sign-off contract: this is a real review, so the normal rules apply — end with reviewed with love by ClauDex 🧡🖤 ONLY if Codex successfully delivered its review; if the Codex call fails (after one retry), end unsigned with the interruption message.

Preflight — it takes two to ClauDex

Run codex --version and check auth (codex login status or equivalent). If either fails, STOP and reply with exactly:

It takes two to ClauDex. 🧡 Claude is here — 🖤 Codex is not, so there is no duet to demo. Fix it in two lines, then come back:

npm i -g @openai/codex
codex login

(No git preflight — the demo brings its own repo.)

The demo

  1. Set the stage. Create a throwaway workspace and repo: DEMO=$(mktemp -d "${TMPDIR:-/tmp}/claudex-demo.XXXXXX") && git -C "$DEMO" init -q

  2. Plant the bugs. Write exactly this to $DEMO/discount.js:

    // discount.js — apply coupon discounts to a shopping cart
    function applyDiscount(cart, coupon) {
      let total = 0;
      for (let i = 0; i <= cart.length; i++) {
        total += cart[i].price * cart[i].qty;
      }
    
      if (coupon.type == "percent") {
        total = total - (total * coupon.value) / 100;
      } else {
        total = total - coupon.value;
      }
    
      cart.forEach((item) => (item.discounted = true));
    
      return "$" + total.toFixed(2);
    }
    
    module.exports = { applyDiscount };
    

    For your own reveal later, the planted issues are: (a) off-by-one i <= cart.length — guaranteed crash; (b) no validation of coupon.value — negative totals, >100% discounts; (c) loose == comparison; (d) the function silently mutates the caller's cart; (e) floating-point money math. Do NOT tell either reviewer this list.

  3. Tell the user what's happening in two sentences: bugs are planted — some obvious, some subtle, one a pure judgment call — and the two models will now review the same file independently.

  4. Claude's review (yours). Review discount.js and write down your findings BEFORE consulting Codex.

  5. Codex's review. With a hard timeout of ~10 minutes:

Read the full file on GitHub · 93 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. yesterday First seen · 93 lines · 22 tokens per session scan C 3a04bf1c1930

Subscribe to this mod's changes

demo is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,019 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other commands, from other repositories

create-pull-request

Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.

xbim08/awesome-claude-code-plugins · 27 tokens

pr-issue-resolve

Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.

xbim08/awesome-claude-code-plugins · 14 tokens

openapi-expert

Use this agent when you need to update, synchronize, or validate the OpenAPI specification (openapi.yml) against the actual REST API implementation. This includes adding new endpoints, updating request/response schemas, fixing discrepancies between the spec and code, or ensuring complete API documentation coverage.

xbim08/awesome-claude-code-plugins · 61 tokens

create-pr

Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.

xbim08/awesome-claude-code-plugins · 31 tokens

husky

Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.

xbim08/awesome-claude-code-plugins · 33 tokens

pr-review

Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.

xbim08/awesome-claude-code-plugins · 23 tokens