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 chen3feng/agent-skills --skill repo-org-migration-url-cleanupgit clone --depth 1 https://github.com/chen3feng/agent-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/chen3feng/agent-skills/repo-org-migration-url-cleanup)<a href="https://agentmods.dev/skills/chen3feng/agent-skills/repo-org-migration-url-cleanup"><img src="https://agentmods.dev/badge/skills/chen3feng/agent-skills/repo-org-migration-url-cleanup/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/chen3feng/agent-skills/repo-org-migration-url-cleanup"><img src="https://agentmods.dev/badge/skills/chen3feng/agent-skills/repo-org-migration-url-cleanup.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.00030 | $0.01613 |
| Opus 5 | $0.00015 | $0.00807 |
| Sonnet 5 | $0.00006 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
repo-org-migration-url-cleanup 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 12d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo-org-migration URL cleanup
When to use
The user tells you a repo has just been transferred on GitHub — from a personal account to an organization, from one org to another, or from Google Code / Bitbucket to GitHub. GitHub's redirect keeps the old URLs "mostly" working, so it's tempting to do nothing, but the redirect is unreliable for things like coveralls project-IDs, README badges fetched by third parties, and anything cached upstream.
Signal phrases: "we moved the repo", "new org", "rename the owner", "dead links after the move", or a link checker flagging old-URL badges.
Problem
Two things go wrong, and they pull in opposite directions:
- Missed URLs — the owner string shows up in a lot more places
than just the README badge you remember:
- Coveralls / Codecov project URLs (GitHub's redirect does not
help the third-party service, which keys by
owner/repo). - Shields.io badges (
img.shields.io/github/downloads/<owner>/<repo>/...). git remote -vexample output embedded in code comments and docstrings.- Issue / PR links in source comments (
# see https://github.com/<old-owner>/<repo>/issues/123). - CI config that hardcodes the clone URL (mostly only self-hosted setups; GitHub Actions usually references the repo implicitly).
pyproject.toml/setup.pyproject-urls,homepage,repositoryfields.- Contrib-rocks / starchart-cc image URLs keyed by
owner/repo.
- Coveralls / Codecov project URLs (GitHub's redirect does not
help the third-party service, which keys by
- Over-eager rewriting — it is wrong to blindly
sedevery<old-owner>/<repo>to<new-owner>/<repo>. Some hits are historical narrative, not live URLs. For example a README paragraph saying "the project was migrated from Google Code to 's personal repository" describes a real event and must not be rewritten to say it was migrated to the new org — that would be fabricating history.
Solution
Do it as a dedicated sweep, separate from any functional change:
- Enumerate categories first (don't just grep blindly). Use the list above as a checklist.
- Run the grep with the exact
owner/repopattern (not just the owner slug, which will match user-names in author fields):
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.
- 12d ago First seen · 149 lines · 30 tokens per session scan A 1731705adbc8
repo-org-migration-url-cleanup is a skill published in the GitHub repository chen3feng/agent-skills (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,613 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
openclaw-dev
OpenClaw Dev Agent — OpenClaw-only docs-aware development assistant. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.
git-forge-migration
Migrate repos between git forges (GitHub/Gitea/Codeberg).
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
update-pr-summary
This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".
github-image-upload
Upload local images and other files (PDF, zip, log, …) to GitHub and embed them in a pull request description, an issue, or a comment — producing canonical github.com/user-attachments URLs (private-repo uploads stay private). Use when asked to "attach a screenshot to the PR", "add an image to the PR description", "put…