move-spec

Move a spec folder between workflow folders (backlog/todo/done).

Command for Claude Code

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/jnarowski/agentcmd/move-spec
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

Made for: Claude Code.

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. Scan, not verified.
Origin unknown 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.00015 $0.01736
Opus 5 $0.00008 $0.00868
Sonnet 5 $0.00003 $0.00347
Haiku 4.5 $0.00002 $0.00174

Measured today against content hash f6a11215b161, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 today.

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. today 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 8mo ago), licensed MIT. It adds 15 tokens to every session and 1,736 once invoked, about $0.0001 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-09-01.