mcp-all-in-one: Command for Claude Code

.claude/commands/openspec/apply.md

apply is a command for Claude Code from vtxf/mcp-all-in-one. It costs 0 tokens per session (296 once invoked), scanned A, a copy of openspec-apply, MIT.

An OpenSpec command for implementing an approved change proposal and updating its task checklist. OpenSpec is a project convention for describing planned software changes before coding them.

In plain words
What is it for?
Use it to read a change proposal, design, and task list, implement the work in order, and mark completed tasks accurately.
Why use it?
It keeps implementation tied to the approved scope and makes it clear whether every planned task is finished.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is vtxf/mcp-all-in-one's own configuration. It tells Claude Code how to work on mcp-all-in-one 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 mcp-all-in-one configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vtxf/mcp-all-in-one. 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/vtxf/mcp-all-in-one/main/.claude/commands/openspec/apply.md
Clone the repo
git clone --depth 1 https://github.com/vtxf/mcp-all-in-one

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 apply

README.md
[![agentmods](https://agentmods.dev/badge/commands/vtxf/mcp-all-in-one/apply/github.svg)](https://agentmods.dev/commands/vtxf/mcp-all-in-one/apply)
Your own site
<a href="https://agentmods.dev/commands/vtxf/mcp-all-in-one/apply"><img src="https://agentmods.dev/badge/commands/vtxf/mcp-all-in-one/apply/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 apply

Your own site · 80×15
<a href="https://agentmods.dev/commands/vtxf/mcp-all-in-one/apply"><img src="https://agentmods.dev/badge/commands/vtxf/mcp-all-in-one/apply.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 296 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 81% copy Near-identical to another mod 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.00296
Opus 5.5 $0.00000 $0.00118
Sonnet 5.5 $0.00000 $0.00059
Haiku 4.5 $0.00000 $0.00030

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

Security

Grade A, and why

apply 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.

Origin

This is a copy

81% identical to openspec-apply — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/openspec/apply.md · 24 lines

What it actually says


name: OpenSpec: Apply description: Implement an approved OpenSpec change and keep tasks in sync. category: OpenSpec tags: [openspec, apply]

Guardrails

  • Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
  • Keep changes tightly scoped to the requested outcome.
  • Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.

Steps Track these steps as TODOs and complete them one by one.

  1. Read changes/<id>/proposal.md, design.md (if present), and tasks.md to confirm scope and acceptance criteria.
  2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
  3. Confirm completion before updating statuses—make sure every item in tasks.md is finished.
  4. Update the checklist after all work is done so each task is marked - [x] and reflects reality.
  5. Reference openspec list or openspec show <item> when additional context is required.

Reference

  • Use openspec show <id> --json --deltas-only if you need additional context from the proposal while implementing.
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 · 24 lines · 0 tokens per session scan A 40966b7d9c49

Subscribe to this mod's changes

apply is a command published in the GitHub repository vtxf/mcp-all-in-one (70 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 296 tokens. A static security scan graded it A with 0 findings. It is 81% identical to openspec-apply, differing in 5 lines, and is treated as a copy.

Related

Other commands, from other repositories

status

A read-only status command for a 10Router instance that reports provider cooldowns, account health, and usage totals. A provider is an external service that supplies requests, while a cooldown temporarily stops use of one that is unavailable or over its limit.

techysy/10router · 83 tokens

sync-usage

A command that exports ZCode model-usage records to 10Router, a service that stores or routes model usage data. It first previews the export and then performs an operation that is safe to repeat.

techysy/10router · 140 tokens

bmad-code-review

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code".

mmornati/leanproxy-mcp · 45 tokens

bmad-review-edge-case-hunter

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

mmornati/leanproxy-mcp · 47 tokens

bmad-advanced-elicitation

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

mmornati/leanproxy-mcp · 48 tokens

bmad-create-story

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".

mmornati/leanproxy-mcp · 37 tokens