founder-os: Command for Claude Code

.claude/commands/queue/approve.md

approve is a command for Claude Code from cloudrepo-io/founder-os. It costs 8 tokens per session (653 once invoked), scanned A, original, MIT.

A command for reviewing a completed research plan and deciding whether it can move to implementation. A research plan is a written proposal for how a task should be investigated or built.

In plain words
What is it for?
Use it to list plans awaiting review, inspect a selected plan, then approve it, reject it, skip it, or send it back for revision.
Why use it?
It keeps implementation work from starting before someone has checked and approved the plan.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is cloudrepo-io/founder-os's own configuration. It tells Claude Code how to work on founder-os 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 founder-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cloudrepo-io/founder-os. 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/cloudrepo-io/founder-os/master/.claude/commands/queue/approve.md
Clone the repo
git clone --depth 1 https://github.com/cloudrepo-io/founder-os

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 approve

README.md
[![agentmods](https://agentmods.dev/badge/commands/cloudrepo-io/founder-os/approve.svg)](https://agentmods.dev/commands/cloudrepo-io/founder-os/approve)
Your own site
<a href="https://agentmods.dev/commands/cloudrepo-io/founder-os/approve"><img src="https://agentmods.dev/badge/commands/cloudrepo-io/founder-os/approve.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 653 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.00008 $0.00653
Opus 5 $0.00004 $0.00327
Sonnet 5 $0.00002 $0.00131
Haiku 4.5 $0.00001 $0.00065

Measured 7d ago against content hash 243011cc4ba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

approve 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 7d 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/queue/approve.md · 87 lines

How it starts

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

Approve Research Plan

Review a completed research plan and approve it for implementation. Approving automatically creates an implementation task.

Arguments

  • $ARGUMENTS - (Optional) Task ID of the plan to approve. If not provided, show all plans awaiting review.

Process

  1. Read .claude/queue/backlog.json to find items with status: "needs_review"

  2. If no task ID provided:

    • List all items with needs_review status
    • Show title, owner, and plan file path for each
    • Ask which plan to review
  3. If task ID provided (or after selection):

    • Read the plan file at the item's plan_file path
    • Display the full plan for review
  4. Present the plan summary and ask for decision:

    Use AskUserQuestion:

    • Question: "How would you like to proceed with this plan?"
    • Options:
      • "Approve" - Accept the plan and create implementation task
      • "Revise" - Request changes to the plan (use /queue:revise instead)
      • "Reject" - Discard the plan entirely
      • "Skip" - Review later

If Approved

  1. Update the research task:

    • Set status: "approved"
    • Add approved_at: "ISO timestamp"
    • Add approved_by: "founder"
  2. Create a new implementation task in backlog:

    {
      "id": "YYYY-MM-DD-{slug}-impl",
      "title": "Implement: {original title without 'Research:' prefix}",
      "type": "implementation",
      "priority": {same as research task},
      "status": "pending",
      "requires_approval": false,
      "owner": "{same owner or reassign}",
      "plan_reference": ".claude/queue/plans/{research-id}.md",
      "blocked_by": [],
      "context": {
        "problem": "{from research task}",
        "acceptance": ["Implement plan as specified in {plan_file}"],
        "files_hint": ["{extracted from plan's Files Affected section}"]
      },
      "sizing": "single-context",
      "created": "ISO timestamp",
      "updated": "ISO timestamp"
    }
    
  3. Move the approved research task to .claude/queue/completed/{id}.json

Read the full file on GitHub · 87 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. 7d ago First seen · 87 lines · 8 tokens per session scan A 243011cc4ba8

Subscribe to this mod's changes

approve is a command published in the GitHub repository cloudrepo-io/founder-os (19 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 653 once invoked, about $0.0000 per session on Opus 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-08-30.