repo-of-repos: Skill for Claude Code

.agents/skills/remove-repository/SKILL.md

remove-repository is a skill for Claude Code from raffertyuy/repo-of-repos. It costs 24 tokens per session (542 once invoked), scanned C, original, MIT.

A repository-removal workflow for deleting a repository or local source folder from the workspace configuration. It updates the repository list, documentation, and ignore rules.

In plain words
What is it for?
Use it to remove a named entry from the repository configuration and documentation, with an explicit choice about deleting its local directory.
Why use it?
Removing only one reference can leave stale configuration or documentation behind. This keeps the workspace records aligned with the repositories that remain.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is raffertyuy/repo-of-repos's own configuration. It tells Claude Code how to work on repo-of-repos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repo-of-repos configures →

Reuse

Borrowing it

Nothing to install: this file belongs to raffertyuy/repo-of-repos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/raffertyuy/repo-of-repos/main/.agents/skills/remove-repository/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/raffertyuy/repo-of-repos

Made for: Claude Code.

Wrote 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.

agentmods badge for remove-repository

README.md
[![agentmods](https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/remove-repository/github.svg)](https://agentmods.dev/skills/raffertyuy/repo-of-repos/remove-repository)
Your own site
<a href="https://agentmods.dev/skills/raffertyuy/repo-of-repos/remove-repository"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/remove-repository/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.

agentmods 80×15 button for remove-repository

Your own site · 80×15
<a href="https://agentmods.dev/skills/raffertyuy/repo-of-repos/remove-repository"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/remove-repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 542 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00542
Opus 5 $0.00012 $0.00271
Sonnet 5 $0.00005 $0.00108
Haiku 4.5 $0.00002 $0.00054

Measured 12d ago against content hash 594bac9f271d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

remove-repository 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 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Run `rm -rf repos/<name>/`
.agents/skills/remove-repository/SKILL.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remove Repository

Remove a single repository or local source folder from the workspace. This is the inverse of /add-repository.

The user will provide a repo name. For example:

  • /remove-repository frontend — remove the frontend entry
  • /remove-repository backend-api — remove the backend-api entry

Behavior

  1. Validate the entry exists in repos/repos.yaml by name

    • If not found, report the error and list available entries so the user can pick the right one
    • If found, proceed
  2. Show what will happen — before taking any action, display:

    • The entry being removed (name, type, URL if git)
    • Whether the directory exists on disk
    • Ask the user: delete the directory from disk too, or just remove the config entry?
  3. Remove from repos/repos.yaml — delete the entry from the repos: list

    • If this was the last entry, leave repos: []
  4. Remove from repos/repos.md — delete the ## <name> section and all its content up to the next ## heading or end of file

    • If no entries remain, restore the placeholder: <!-- No repositories found. Clone repos into repos/ and run /pull-all-repos to populate this file. -->
  5. Update .gitignore — if repos/<name>/ appears in .gitignore (whether git repo or gitignored local folder), remove the line. No need to ask — if the entry is being removed, its gitignore line should go too.

  6. Optionally delete from disk — only if the user confirmed deletion in step 2:

    • Run rm -rf repos/<name>/
    • If the user said no, leave the directory in place (it becomes an orphan that /pull-all-repos would re-register)
  7. Report what was done:

    Removed <name> from repos.yaml, repos.md, and .gitignore. Directory on disk: deleted / kept.

Notes

  • Always ask before deleting from disk — never auto-delete
  • If the directory has uncommitted changes (for git repos), warn the user before they confirm deletion
  • This skill does NOT push or modify anything in the sub-repo's own git history

Read the full file on GitHub · 47 lines

Changes

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.

  1. 12d ago First seen · 47 lines · 24 tokens per session scan C 594bac9f271d

Subscribe to this mod's changes

remove-repository is a skill published in the GitHub repository raffertyuy/repo-of-repos (12 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 542 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens