Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MostAshraf/ai-sdlc-harness/plugin install ai-sdlc-harnessWrote 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/skills/mostashraf/ai-sdlc-harness/migrate-workspace)<a href="https://agentmods.dev/skills/mostashraf/ai-sdlc-harness/migrate-workspace"><img src="https://agentmods.dev/badge/skills/mostashraf/ai-sdlc-harness/migrate-workspace/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.
<a href="https://agentmods.dev/skills/mostashraf/ai-sdlc-harness/migrate-workspace"><img src="https://agentmods.dev/badge/skills/mostashraf/ai-sdlc-harness/migrate-workspace.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.01437 |
| Opus 5 | $0.00035 | $0.00718 |
| Sonnet 5 | $0.00014 | $0.00287 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
migrate-workspace 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 9d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate-workspace — adopt a v2.x workspace
The fork seam: this file and harness/migrate.py are the replaceable
unit — forks ship different adoption logic by swapping them and nothing
else. Everything that WRITES goes through the same owned path as
/init-workspace (init-section → init-verify → init-finalize);
migrate verbs are read-only proposals.
Human-only, same invocation rules as every skill here: always the full
${CLAUDE_PLUGIN_ROOT}/bin/harness <verb> path. First run
/init-workspace's step 0 environment bootstrap exactly as written
there (that file owns the procedure — don't re-derive it).
1 · Detect (stop conditions first)
${CLAUDE_PLUGIN_ROOT}/bin/harness migrate-detect
- Surface
warningsverbatim whenever present — e.g. an unreadableoverrides.yamlreports as bootstrapped fail-closed, and the remediation lives in the warning, not here. already_bootstrapped: true→ this workspace already runs v3.0. Ifinventory.legacy_context_filesis non-empty, a prior migration stopped before archiving — offer the archive-only finish (steps 5–6; the report on this path recordsinventoryonly, sincemigrate-extractrightly refuses post-bootstrap — the carried-config record lives in the earlier attempt's confirmations); otherwise stop and point the user at/workspace-config.legacy: null→ stop: nothing to adopt; point at/init-workspace.- Otherwise show the
evidencelist (why this looks like v2.x), then theinventory:in_flightruns get a hard boundary, stated plainly: run history is never converted — v3.0 state is sealed evidence (red-proofs, ledgers) that v2.x never produced, so migrating a half-done run would fabricate its audit trail. Recommend finishing or abandoning those stories on v2.x before migrating: step 5 archives the very config files v2.x resumes from, so proceeding now means a later v2.x session must first hand-restore them fromlegacy-2.1/. Proceeding anyway is the user's call — record the choice in the step-5 report.- Old
ai/run dirs andabortedleftovers stay exactly where they are as readable archives; v3.0 run discovery ignores them.
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.
- 9d ago First seen · 121 lines · 70 tokens per session scan A 7940da62bfba
migrate-workspace is a skill published in the GitHub repository MostAshraf/ai-sdlc-harness (18 stars, last pushed 12d ago), licensed MIT. It adds 70 tokens to every session and 1,437 once invoked, about $0.0003 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 skills, from other repositories
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
explore
Explore ideas, think through approaches, and route insights to the right artifacts.
resume
Pick up where you left off. Restores context and suggests next action.