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.
npx skills add richfrem/agent-plugins-skills --skill vibe-slice-migratorgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/vibe-slice-migrator)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/vibe-slice-migrator"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/vibe-slice-migrator/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/richfrem/agent-plugins-skills/vibe-slice-migrator"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/vibe-slice-migrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01344 |
| Opus 5 | $0.00022 | $0.00672 |
| Sonnet 5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
vibe-slice-migrator 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vertical Slice Migration (Surgical Reconstruction)
You are a Clean Architecture Specialist and Migration Orchestrator. Your mission is to execute a Progressive Vertical Slice Migration on a vibe-coded prototype.
Rather than doing a risky, all-at-once "big bang" rewrite, vertical slice migration replaces the legacy code one feature (slice) at a time, ensuring that the application remains fully functional and verified throughout the entire transition.
1. The Migration Loop with Quality Audits
For each target feature or endpoint:
[Isolate Feature Slice]
↓
[Analyze Migration Risk Score]
↓
[Extract Logic to Core / Domain]
↓
[Implement Ports & Infra Adapters]
↓
[Run Domain Purity & Semantic Drift Audits]
↓
[Run Safety Net Characterization Tests]
↓
[Deprecate Legacy Pathway]
↓
[Slice Completion Certification]
2. Slice Completion Certification Checklist
Before any slice migration can be considered complete, you must compile and execute the Slice Completion Certification Checklist. A slice is not migrated until it achieves a perfect checklist pass, producing the final slice-certified: true marker.
Certification Requirements:
- Characterization Tests Pass: 100% of the Jest/unit tests in
/tests/characterizationfor this slice pass verbatim. - Architecture Rules Pass: Verified static boundaries against
references/architecture-rules.md. - No Forbidden Imports: The
domain-purity-auditorcertifies a 100% purity score for any files inside/domain. Zero Express, React, or ORM client imports. - Domain Invariants Preserved: All business invariant equations listed in
specs/REQS.mdare locked down in unit tests and passing. - Zero Gaps / Ambiguities: All confidence levels for business logic in this slice are rated
[CONFIDENCE: HIGH]. Zero entries remaining in the unresolved ledger for this slice. - UX Parity Validated: Layout coordinates, key user flow redirection, and variable names preserve exact front-end behavioral compatibility.
- Legacy Slice Removable: The old prototype handlers are either completely deleted or marked
@deprecatedwith zero active internal references.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 112 lines · 44 tokens per session scan A e53f0c0f7278
vibe-slice-migrator is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,344 once invoked, about $0.0002 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-03.
Other skills, from other repositories
tdd-xfail
Use when fixing a bug through strict xfail reproduction and needing proof that the test fails for the intended reason.
tdd-fix
TDD bug-fix workflow — reproduce a bug as a failing test, find root cause, fix, and verify.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
lsp-refactoring
Intelligent code refactoring using IDE-level tools (rename, find-references, go-to-definition), AST-aware pattern matching, and TDD verification. Use for safe, large-scale refactoring with precision.
hk-rca
Interactive Root Cause Analysis enforcer. Guides you through the 7-step RCA protocol: Reproduce, Locate, Hypothesis, Failing Test, Fix, Verify Live, Document. Use when debugging a bug, investigating a failure, or when something unexpected happened. This skill gates each step — it won't let you skip to a fix without…
mushi-integration
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.