agentcmd: Command for Claude Code

.claude/commands/cmd/move-spec.md

move-spec is a command for Claude Code from jnarowski/agentcmd. It costs 15 tokens per session (1,736 once invoked), scanned A, original, MIT.

A workflow command for moving a feature specification between backlog, todo, and done folders while updating its status.

In plain words
What is it for?
Use it to find a specification by ID, name, or path, move it, and update its metadata and index entry.
Why use it?
It keeps the file location, index, and workflow status aligned when a piece of planned work changes state.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

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

Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/cmd/move-spec.md
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

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 move-spec

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/move-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/move-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 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,736 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.00015 $0.01736
Opus 5.5 $0.00006 $0.00694
Sonnet 5.5 $0.00003 $0.00347
Haiku 4.5 $0.00002 $0.00174

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

Security

Grade A, and why

move-spec 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 2mo 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/cmd/move-spec.md · 208 lines

How it starts

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

Move Spec

Move a spec folder between workflow folders (backlog/todo/done), update index.json, and optionally update status field.

Variables

  • $specIdOrNameOrPath: $1 (required) - Either a timestamp ID (e.g., 2510241201), feature name (e.g., workflow-safety), or full path (e.g., .agent/specs/todo/2510241201-workflow-safety/)
  • $targetFolder: $2 (required) - Target workflow folder: "backlog", "todo", or "done"

Instructions

  • Search for the spec folder in all locations (backlog/, todo/, done/)
  • Move the entire folder to the target folder
  • Update index.json with new location
  • Update the Status field in spec.md front matter based on target folder
  • Support both old single-file specs and new folder-based specs
  • Report the old and new paths

Workflow

  1. Find the Spec Folder or File

    • Parse and resolve $specIdOrNameOrPath:
      • If it's a full path (contains /):
        • Use the path as-is
      • Otherwise, look up in .agent/specs/index.json:
        • For timestamp ID: Match by id field
        • For feature name: Fuzzy match path (e.g., message-queue matches todo/2510241201-message-queue-implementation/spec.md)
        • Use path from index: .agent/specs/{path} (extract folder from file path: dirname({path}))
      • If not found in index.json, fallback to directory search:
        • Search in order: .agent/specs/backlog/, .agent/specs/todo/, .agent/specs/done/
        • For ID: Pattern {id}-*/
        • For feature name: Pattern *{feature-name}*/ (fuzzy match)
    • If still not found, report error and exit
  2. Validate Target Folder

    • Ensure $targetFolder is one of: "backlog", "todo", or "done"
    • If invalid, report error and exit
  3. Check for Conflicts

    • Check if a folder/file with the same name already exists in target folder
    • If conflict exists, report error and exit
  4. Move the Folder

    • Move entire folder from current location to .agent/specs/${targetFolder}/[foldername]
    • Preserve the original folder name

Read the full file on GitHub · 208 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. 2mo ago First seen · 208 lines · 15 tokens per session scan A f6a11215b161

Subscribe to this mod's changes

move-spec is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 15 tokens to every session and 1,736 once invoked, about $0.0001 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-09-01.

Related

move-spec compared with commands from other repositories

move-spec next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
move-specjnarowski/agentcmdCommand1810mo agoMITA15Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code