agentmods.dev

smith-migrate-specs

smith-migrate-specs is a skill for Claude Code, Codex from ATTCKDigital/smith. It costs 26 tokens per session (1,445 once invoked), scanned A, original, MIT.

A migration tool for moving feature specification folders into a hierarchy grouped by system. It works within an active Smith workflow and uses existing system specification files to choose each feature’s destination.

In plain words
What is it for?
Use it to scan the specs/ folder, identify numbered feature folders, and move them under .specify/systems/<system>/features/. It skips folders and files that are not feature specifications.
Why use it?
It removes the need to move and organize many specification folders by hand. It also helps keep older feature specifications in the same structure as newer ones.

Skill for Claude CodeCodex

Part of the smith plugin — 32 skills, 7 agents shipped together

not rated 52 1mo ago A scan 26 tokens original MIT
View the source file ATTCKDigital/smith
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 skills/attckdigital/smith/smith-migrate-specs
Any agent
npx skills add ATTCKDigital/smith --skill smith-migrate-specs
Clone the repo
git clone --depth 1 https://github.com/ATTCKDigital/smith

Made for: Claude Code, Codex.

Or install smith, the plugin that ships this one along with the rest of its 32 skills, 7 agents.

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 smith-migrate-specs

README.md
[![agentmods](https://agentmods.dev/badge/skills/attckdigital/smith/smith-migrate-specs.svg)](https://agentmods.dev/skills/attckdigital/smith/smith-migrate-specs)
Your own site
<a href="https://agentmods.dev/skills/attckdigital/smith/smith-migrate-specs"><img src="https://agentmods.dev/badge/skills/attckdigital/smith/smith-migrate-specs.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,445 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00026 $0.01445
Opus 5 $0.00013 $0.00723
Sonnet 5 $0.00005 $0.00289
Haiku 4.5 $0.00003 $0.00145

Measured 4d ago against content hash be3439929852, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

smith-migrate-specs 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 4d 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.

skills/smith-migrate-specs/SKILL.md · 143 lines

How it starts

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

Workflow requirement (Smith 20+): This skill must be invoked from inside an active top-level workflow (/smith-new, /smith-bugfix, /smith-debug, /smith-build). The workflow-gate hook will block standalone invocation. To use this skill standalone, start a top-level workflow first.

Smith Spec Migration

Migrate existing feature spec folders from specs/<NNN-feature>/ into the system-based hierarchy at .specify/systems/<system>/features/<NNN-feature>/.

Arguments: $ARGUMENTS

Prerequisites

  • .specify/systems/ must exist with system spec folders (created by Phase 1B setup or /smith)
  • System spec files must be present at .specify/systems/system-*/spec.md for system detection to work

Behavior

Step 1: Scan for Migratable Features

Scan specs/ for all feature spec folders. Exclude the following (they are not feature specs):

  • specs/system-* (system specs — these are the source of truth)
  • specs/questions/ (global questions directory)
  • specs/screenshots/ (visual reference)
  • specs/sentiment-engine/ (legacy non-numbered spec)
  • specs/init-intake.md (not a folder)

A valid feature folder must:

  • Be a directory
  • Contain at least a spec.md file
  • Match the pattern NNN-* (numbered feature)

List all candidates with their folder name and a one-line summary from the first heading in their spec.md.

Step 2: System Detection (per feature)

For each feature folder, determine the primary system:

  1. Read the feature's spec.md — extract what the feature does, which services it touches, what data it modifies
  2. Read all .specify/systems/system-*/spec.md — understand each system's scope
  3. Determine primary_system — the system most directly impacted by the feature
  4. Determine also_affects — other systems the feature touches

Use these heuristics for mapping:

  • Features touching services/command-center/ → system-15-command-center
  • Features touching services/email-pipeline/ → system-03-email-archive-contact-graph
  • Features touching services/sentiment-engine/ → system-05-communication-triage or system-03 depending on scope
  • Features touching services/content-strategy/ or services/content-engine/ → system-12-content-social-engine
  • Features touching services/social-listening/ → system-10-social-listening
  • Features touching services/trend-intelligence/ → system-13-trend-intelligence
  • Features touching services/voice-training/ → system-04-personal-voice
  • Features touching services/meeting-intelligence/ → system-09-meeting-intelligence
  • Features touching docker-compose.yml or infrastructure → system-01-infrastructure
  • Features touching Neo4j/contacts/graph → system-03-email-archive-contact-graph
  • Features touching N8N workflows → system-01-infrastructure
  • Features that are genuinely cross-cutting → cross-system

Read the full file on GitHub · 143 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. 4d ago First seen · 143 lines · 26 tokens per session scan A be3439929852

Subscribe to this mod's changes

smith-migrate-specs is a skill published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,445 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-08-30.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens