repo-prep

repo-prep is a skill for Claude Code, Codex from glebis/claude-skills. It costs 158 tokens per session (1,518 once invoked), scanned A, original, MIT.

An interactive setup workflow for preparing a code repository for publication or open source release. It creates or updates files such as licenses, README sections, contribution guides, security policies, and issue templates.

In plain words
What is it for?
It is for preparing repositories for GitHub, documenting AI-assisted authorship, adding project policies, and checking relevant EU or German requirements.
Why use it?
It helps identify missing legal, metadata, community, and compliance documents before a repository is shared publicly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions AGENTS.md.

Good fit It is for preparing repositories for GitHub, documenting AI-assisted authorship, adding project policies, and checking relevant EU or German requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/glebis/claude-skills/repo-prep
Install

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.

Any agent
npx skills add glebis/claude-skills --skill repo-prep
Clone the repo
git clone --depth 1 https://github.com/glebis/claude-skills

Made for: Claude Code, Codex.

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 repo-prep

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/glebis/claude-skills/repo-prep"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/repo-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00158 $0.01518
Opus 5 $0.00079 $0.00759
Sonnet 5 $0.00032 $0.00304
Haiku 4.5 $0.00016 $0.00152

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

Security

Grade A, and why

repo-prep 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/fetch_license.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

repo-prep/SKILL.md · 117 lines

How it starts

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

Repo Prep

Interactively scaffold the legal, metadata, community, and compliance files a repository needs before publication — consistently, from a central author profile, with author choices respected per repo.

When to use

  • Preparing a new or existing repo for GitHub / open-sourcing.
  • Adding missing LICENSE, NOTICE, AUTHORSHIP, README sections, or package metadata.
  • Writing a defensible AUTHORSHIP record for AI-assisted work (the wizard).
  • Adding community docs or .github/ templates.
  • Checking EU/Germany compliance obligations for a repo.

Operating principles

  • Interactive, not assumed. Ask the user for choices (see Asking questions below); respect the author profile's defaults but confirm per repo. Don't blindly dump templates.
  • Idempotent. Detect what already exists; skip or refresh, never clobber silently. Show a plan before writing.
  • Evidence over assertion (especially authorship): mine the repo for facts.
  • Confirm outward-facing actions (anything via gh, pushes) before running.
  • Follow the user's git conventions — commit only when asked.

Asking questions (interview transport)

Prefer cenno when it is installed — it gives a nicer panel, progress dots, and voice input (great for the reflective authorship answers).

  1. Detect cenno once per run: ToolSearch for mcp__cenno__ask_sequence. If the tools resolve, use cenno; otherwise fall back to AskUserQuestion (choices) / plain conversational prompts (free text).
  2. When using cenno:
    • Multi-question flows (the authorship wizard, scope selection) → mcp__cenno__ask_sequence with flow: "question"; it auto-fills progress dots.
    • Single questions → mcp__cenno__ask_user.
    • Use input.kind: "choice" + choices for pick-one; "confirm" for yes/no; "voice_text" for reflective free-text (Decisions, Judgment, Direction, Art Direction); "scale" for ratings.
    • Parse the returned JSON ({answers: [...]} / {answer, ...}). Handle {answered: false} (timeout) by retrying or falling back.
  3. If cenno is wanted but not installed, mention it can be set up via the cenno skill; do not block — fall back gracefully.

Read the full file on GitHub · 117 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. 8d ago First seen · 117 lines · 158 tokens per session scan A 73dcfaca80bc

Subscribe to this mod's changes

repo-prep is a skill published in the GitHub repository glebis/claude-skills (375 stars, last pushed 10d ago), licensed MIT. It adds 158 tokens to every session and 1,518 once invoked, about $0.0008 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-09-03.

Related

Other skills, from other repositories

open-sourcing

This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering…

trailofbits/skills · 82 tokens

compliance-license-audit

Interactive open-source license compliance audit to identify all dependency licenses, flag risks, and detect license incompatibilities.

charlesjones-dev/claude-code-plugins-dev · 27 tokens

compliance-notice-generate

Generate NOTICE, ATTRIBUTION, or THIRD-PARTY-NOTICES files from detected dependency licenses to fulfill open-source license obligations.

charlesjones-dev/claude-code-plugins-dev · 34 tokens

open-source

Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODEOFCONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA"…

claude-dev-suite/claude-dev-suite · 150 tokens

community-health

Guide for setting up GitHub community health files for open source repositories. Use when preparing repos for public release, adding community standards files, or configuring issue/PR templates.

vinnie357/claude-skills · 37 tokens

release-guard

Block releases that fail the licence and changelog policy, and bundle the team's release tooling into one installable package.

eugenelim/agent-ready-repo · 27 tokens