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 Dragoon0x/everything-design-taste --skill content-migrationgit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/content-migration)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/content-migration"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/content-migration.svg" alt="Measured on agentmods" 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.00016 | $0.00235 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
content-migration 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.
What it actually says
Content Migration
Content Audit Process
- Inventory: Catalog all content (pages, posts, assets, documents).
- Assess: Score each piece on accuracy, usefulness, quality, and alignment.
- Decide: Keep as-is, revise, merge, archive, or delete.
- Plan: Map content to new structure.
- Execute: Migrate in phases, not all at once.
Migration Checklist
- URL redirect map (old → new)
- Image/asset inventory and migration
- SEO metadata preserved or improved
- Internal links updated
- 404 monitoring post-launch
- Analytics baseline captured before migration
Common Mistakes
- Migrating everything (including outdated, redundant content).
- Not setting up redirects (SEO disaster).
- Losing metadata during migration.
- Not testing content in the new design before launch.
- Migrating without an editorial review.
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.
- 4d ago First seen · 30 lines · 16 tokens per session scan A ca7ae0e5ae4f
content-migration is a skill published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 235 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-03.
Other skills, from other repositories
implement-github-feature
Design and implement a new feature or component from a GitHub issue. Use for net-new functionality, not bug fixes.
fix-github-issue
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
product-marketing
Product management and marketing strategy — positioning, discovery, go-to-market, prioritization, metrics, copywriting, and artifact generation. Verified against Cagan (SVPG), Dunford, Torres, Reforge, JTBD, and OWASP-grade rigor applied to PM/PMM decisions.
product-discovery-and-framing
Frame product opportunities from user, business, technical, and market evidence into testable problem statements, priorities, risks, and success criteria. Use before solution design when the team is unsure what problem to solve or why it matters.
multi-agent-kanban
Coordinate multiple local agents through a durable board with owner, state, and evidence fields.
linear-sync
Linear integration for Mémoire — sync design issues, component specs, and project tracking between Linear and the Mémoire registry.