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 ellmos-ai/skills --skill migrate-renamegit clone --depth 1 https://github.com/ellmos-ai/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/ellmos-ai/skills/migrate-rename)<a href="https://agentmods.dev/skills/ellmos-ai/skills/migrate-rename"><img src="https://agentmods.dev/badge/skills/ellmos-ai/skills/migrate-rename/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/ellmos-ai/skills/migrate-rename"><img src="https://agentmods.dev/badge/skills/ellmos-ai/skills/migrate-rename.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.00042 | $0.01664 |
| Opus 5 | $0.00021 | $0.00832 |
| Sonnet 5 | $0.00008 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00166 |
Grade A, and why
migrate-rename 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datei-Umbenennung mit Wrapper (Evolutionaere Migration)
Ermoeglicht Datei-Umbenennungen OHNE harte Brueche. Verweise werden organisch durch taegliche Nutzung aktualisiert.
Prinzip: Evolutionaere Migration
VORHER: NACHHER:
alte_datei.md neue_datei.md (umbenannt)
| |
+-- Verweis A +-- alte_datei.md (Wrapper)
+-- Verweis B |
+-- Verweis C +-- Log-Tabelle
+-- Anleitung
+-- Link zu neue_datei.md
Wer den alten Pfad aufruft:
- Landet bei der Wrapper-Datei
- Traegt sich ins Log ein
- Korrigiert den Verweis der ihn herschickte
- Geht zur eigentlichen Datei
Schritt-fuer-Schritt
1. Datei umbenennen
mv alte_datei.md neue_datei.md
2. Wrapper-Datei erstellen
Erstelle alte_datei.md mit folgendem Inhalt:
# ALTE_DATEI.md - UMGELEITET
**Status:** Diese Datei wurde umbenannt zu `neue_datei.md`
---
## Migration-Log
| Datum | Wer | Herkunft | Verweis korrigiert? |
|-------|-----|----------|---------------------|
| YYYY-MM-DD | [Name] | Initiale Migration | n/a (Wrapper erstellt) |
---
## Anleitung
1. **Log-Eintrag hinterlassen** (oben in Tabelle)
2. **Herkunft pruefen**: Was hat dich hierher geschickt?
3. **Verweis korrigieren**: Aendere `alte_datei.md` -> `neue_datei.md`
4. **Zur eigentlichen Datei gehen**: [neue_datei.md](neue_datei.md)
---
**Zieldatei:** [neue_datei.md](neue_datei.md)
3. Kritische Verweise sofort korrigieren
- Help-Dateien (primaere Dokumentation)
- System-Prompt Referenzen
- CLI-Code der den Pfad direkt verwendet
4. Uebrige Verweise evolutionaer migrieren
Der Rest wird automatisch korrigiert bei Nutzung.
Wann Wrapper-Methode verwenden?
JA - Wrapper sinnvoll:
- Viele potenzielle Verweise
- Datei wird von verschiedenen Partnern/Tools referenziert
- Keine kritische System-Datei
What ships with it
13 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.
- 4d ago Changed · +53 lines · +14 tokens per session 14803f2542d8
- 11d ago First seen · 130 lines · 28 tokens per session scan A 706398746ea2
migrate-rename is a skill published in the GitHub repository ellmos-ai/skills (4 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,664 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-08-31.
Other skills, from other repositories
prep-repo
Use when the user wants to prepare a local project for GitHub or public release. Runs a release-readiness sweep over README structure, bilingual docs, commit hygiene, sensitive-data exposure, broken links, markdown rendering, project layout, tests, CI, Docker, and final cleanup. Fixes issues only inside the target…
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
accelerate
Run PyTorch training across GPUs with minimal changes.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.