AI Agent Skills is a curated library and package manager for installing, organizing, and creating skills for compatible AI coding agents. It is for developers who want to manage reusable agent instructions through a command-line or terminal interface. The catalogue skills and agents are examples of the kind of add-ons it helps manage.
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 MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-librariesgit clone --depth 1 https://github.com/MoizIbnYousaf/Ai-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/moizibnyousaf/ai-agent-skills/migrate-skills-between-libraries)<a href="https://agentmods.dev/skills/moizibnyousaf/ai-agent-skills/migrate-skills-between-libraries"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/ai-agent-skills/migrate-skills-between-libraries/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/moizibnyousaf/ai-agent-skills/migrate-skills-between-libraries"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/ai-agent-skills/migrate-skills-between-libraries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 19 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 30 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 49 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 55 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 61 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00036 | $0.00617 |
| Opus 5.5 | $0.00014 | $0.00247 |
| Sonnet 5.5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
migrate-skills-between-libraries 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Skills Between Libraries
Goal
Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
Guardrails
- Always use
--dry-runbefore any mutating command in the target workspace. - Always use
--listto inspect the source library before importing. - Always use
--format jsonfor structured output when scripting migrations. - Never import skills without checking for name collisions in the target workspace first.
- Always run
build-docsin the target workspace after migration.
Workflow
Export: Identify skills to migrate from the source library
- List all skills in the source workspace.
cd /path/to/source-library
npx ai-agent-skills list --format json --fields name,tier,workArea,collections
- For house copies, note the skill folder paths. For upstream picks, note the installSource.
Import: Add skills to the target workspace
- For house copies, use
vendorto copy the skill folder into the target:
cd /path/to/target-library
npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run
npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
- For upstream picks, use
catalogto re-catalog from the original source:
npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run
npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
- Rebuild docs in the target workspace.
npx ai-agent-skills build-docs
- Validate the target workspace.
npx ai-agent-skills validate
Gotchas
- Skill names must be unique per workspace. Check for collisions before importing.
- House copies are full folder copies — the source and target are independent after migration.
- Upstream picks re-catalog from the original upstream source, not the intermediate library.
- Dependencies (
requiresfield) must also be migrated. Checkinfo --format jsonfor each skill's dependency graph. - Collection membership does not transfer automatically. Use
curate --collection <id>to add migrated skills to target collections.
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.
- 1mo ago First seen · 71 lines · 36 tokens per session scan A 2ff7cb86176f
migrate-skills-between-libraries is a skill published in the GitHub repository MoizIbnYousaf/Ai-Agent-Skills (1,152 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 617 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
pad
Work with the user's Pad workspaces through the Pad tools. Find, read, create and update tasks, bugs, ideas, plans and docs; comment on them, link them, and see what to work on next. Use it whenever the user talks about their Pad projects or items.
promo-video-pipeline
A workflow for producing promotional videos with Remotion, a React-based tool that renders video from code. It splits a storyboard into scenes, assigns work to separate agents, combines the results, and checks the actual rendered video.
connect
Connect this session to Pad's push/watch stream — consent to receive pushes, and run the workspace's on-session-start ritual on first connect.
status
Project status at a glance — dashboard, active plans, attention items.