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.
curl -O https://raw.githubusercontent.com/cloudrepo-io/founder-os/master/.claude/commands/queue/approve.mdgit clone --depth 1 https://github.com/cloudrepo-io/founder-osWrote 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.
[](https://agentmods.dev/commands/cloudrepo-io/founder-os/approve)<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>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.
| Model | Per session | Once 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 |
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.
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
-
Read
.claude/queue/backlog.jsonto find items withstatus: "needs_review" -
If no task ID provided:
- List all items with
needs_reviewstatus - Show title, owner, and plan file path for each
- Ask which plan to review
- List all items with
-
If task ID provided (or after selection):
- Read the plan file at the item's
plan_filepath - Display the full plan for review
- Read the plan file at the item's
-
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:reviseinstead) - "Reject" - Discard the plan entirely
- "Skip" - Review later
If Approved
-
Update the research task:
- Set
status: "approved" - Add
approved_at: "ISO timestamp" - Add
approved_by: "founder"
- Set
-
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" } -
Move the approved research task to
.claude/queue/completed/{id}.json
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.
- 7d ago First seen · 87 lines · 8 tokens per session scan A 243011cc4ba8
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.