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 agentmods add skills/nicepkg/ai-workflow/remove-old-skills-from-workflownpx skills add nicepkg/ai-workflow --skill remove-old-skills-from-workflowgit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/remove-old-skills-from-workflow)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/remove-old-skills-from-workflow"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/remove-old-skills-from-workflow.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.00053 | $0.00765 |
| Opus 5 | $0.00026 | $0.00382 |
| Sonnet 5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade C, and why
remove-old-skills-from-workflow scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /path/to/workflow/.claude/skills/skill-name/ How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Skills from Workflow
Guide for removing skills from an existing workflow and updating all related documentation.
When to Use
- User wants to remove a skill from a workflow
- User says "remove skill", "delete skill", "移除技能", "删除技能"
- Cleaning up unused or deprecated skills from a workflow
Removal Workflow
Step 1: Identify the Skill
Search for the skill name across the workflow to understand its usage:
# Find all references to the skill
grep -r "skill-name" /path/to/workflow/
Step 2: Delete Skill Folder
Remove the skill directory from the workflow:
rm -rf /path/to/workflow/.claude/skills/skill-name/
Step 3: Update skill-source.json (if exists)
Remove the skill entry from /path/to/workflow/.claude/skill-source.json
Step 4: Update All Related Documentation
After removing a skill, you MUST update these files:
Files to Update (7 files)
| File | What to Update |
|---|---|
workflows/<workflow-name>/README.md |
Skill count, skill table, pipeline stages, skill combinations |
workflows/<workflow-name>/README_cn.md |
Same as above (Chinese version) |
workflows/<workflow-name>/AGENTS.md |
Available skills list, recommended sequences |
website/content/en/workflows/<workflow>.mdx |
Skill count, skill table, pipeline, skill combinations |
website/content/zh/workflows/<workflow>.mdx |
Same as above (Chinese version) |
README.md (root) |
Workflow table skill count |
README_cn.md (root) |
Workflow table skill count (Chinese version) |
Documentation Update Checklist
For each documentation file, update:
- Skill count: Decrease the total skill count (e.g., "20 skills" → "19 skills")
- Skill tables: Remove the skill row from any skill listing tables
- Pipeline/stages: Remove skill references from pipeline diagrams or stage descriptions
- Skill combinations: Remove any skill chains that include the removed skill
- Example workflows: Remove or update examples that reference the skill
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.
- 6d ago First seen · 92 lines · 53 tokens per session scan C 81f0cf5a80aa
remove-old-skills-from-workflow is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 765 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
ensembl-database
Query Ensembl genome database REST API for 250+ species. Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions, for genomic research.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
wukongim-cloud-analysis
Diagnose one exact live WuKongIM cloud Simulation Run or chat-lifecycle Cloud Lease through the repository Analysis MCP. Use when the user or a local Analysis Session asks Codex to inspect a run's cluster state, Prometheus signals, application logs, diagnostics, Controller task audits, profiles, or redacted config…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
lazarus-group
Adversary-emulation profile for Lazarus Group (G0032, aka Hidden Cobra / Diamond Sleet / Labyrinth Chollima), a North Korean RGB-linked actor conducting espionage, destructive, and financially motivated operations.