Borrowing it
Nothing to install: this file belongs to hlop3z/claude-ai-dangerous. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlop3z/claude-ai-dangerous/main/.claude/commands/ai/migration.mdgit clone --depth 1 https://github.com/hlop3z/claude-ai-dangerousWrote 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/commands/hlop3z/claude-ai-dangerous/migration)<a href="https://agentmods.dev/commands/hlop3z/claude-ai-dangerous/migration"><img src="https://agentmods.dev/badge/commands/hlop3z/claude-ai-dangerous/migration/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/commands/hlop3z/claude-ai-dangerous/migration"><img src="https://agentmods.dev/badge/commands/hlop3z/claude-ai-dangerous/migration.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.00026 | $0.01403 |
| Opus 5 | $0.00013 | $0.00701 |
| Sonnet 5 | $0.00005 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade C, and why
AI: Migration scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Every build-vs-adopt decision that shaped the system. --> How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distill everything that matters from the OpenSpec workflow into one self-contained file
(PROJECT.md at the project root) so the user can delete openspec/ — config, specs,
changes, tasks — and still retain the core of what the project is, why, and how it was
decided. This is a consolidation, not a snapshot: OpenSpec is going away, so the output
must stand on its own with zero pointers back into openspec/.
The canon is not in scope. .canon/ is ours and survives OpenSpec's removal untouched —
so PROJECT.md must NOT absorb, duplicate, or condense the engineering rules and guidelines.
Pointing at .canon/ is correct here; copying it in would create a second home for rules that
already have one.
This is the inverse of /ai:handoff. Handoff references canonical homes and stays
gitignored. Migration absorbs those homes into a single committed file that becomes the
new canonical home once OpenSpec is removed.
What to keep (the things that matter most)
Include only durable essence. When in doubt, ask: "if OpenSpec were deleted tomorrow, would losing this hurt?" If no, drop it.
- Capability contracts — for each capability in
openspec/specs/, its purpose and its core requirements/invariants (the MUST/SHOULD behavior that must hold). Condense scenarios to the invariant they protect; drop exhaustive WHEN/THEN tables. - Architecture — the structural shape: core vs adapters, inward-only dependency direction, workspace/crate layout, where composition wiring lives. The HOW that outlives any single change.
- Decisions (ADRs) — every recorded build-vs-adopt decision from the
design.mdADR blocks across all changes (active and archived): the concern, the choice (Rent/Adopt/Extend/Fork/Build), the chosen tool, and the one-line why. This is the highest- value content — decisions and their rationale are the least recoverable from code. - Chosen tech stack — the concrete tools/vendors actually selected (languages, backends, libraries), each tied to the decision that picked it.
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 · 122 lines · 26 tokens per session scan C 109d0bf712fc
AI: Migration is a command published in the GitHub repository hlop3z/claude-ai-dangerous (2 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 1,403 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Archive
Archive a completed change in the experimental workflow.
project-brief
Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
pr-summary
PR status summary — list open PRs, filter bots, group by ticket ID.
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.