Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.
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 daymade/claude-code-skills --skill auto-repo-setupgit clone --depth 1 https://github.com/daymade/claude-code-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/daymade/claude-code-skills/auto-repo-setup)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/auto-repo-setup"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/auto-repo-setup.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Privilege Escalation · line 45 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 107 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00112 | $0.02218 |
| Opus 5 | $0.00056 | $0.01109 |
| Sonnet 5 | $0.00022 | $0.00444 |
| Haiku 4.5 | $0.00011 | $0.00222 |
Grade A, and why
auto-repo-setup 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.
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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Repo Setup
Make the repository usable without changing the user's normal way of working. Treat setup as an evidence-driven repository task, not as a special interface for people with a particular job title.
Entry router
Classify the request before changing anything. Do not combine modes merely because they all contain the word "setup".
| User outcome | Mode | First action |
|---|---|---|
| "It won't run", missing dependency, new machine | Environment repair | Read project instructions and detect the actual stack |
| "Sync before we work", "pull the latest" | Session routine | Use project instructions or execute the user's natural-language request |
| Repeated or unexpected hook output | Hook diagnosis | Count registrations and firing sessions before editing configuration |
| A teammate needs a repeatable handoff | Repository handoff | Audit existing onboarding and fill only the missing operational contract |
| Commit, push, conflict, leaked secret/history | Git safety | Read references/git_safety.md before mutation |
| Behavior must happen before the first prompt | Startup automation | Read references/startup_automation.md and pass its hook gate |
Operating principles
- Do not infer competence from role. Match the user's demonstrated altitude. A collaborator can tell an agent "sync the remote first"; do not invent a launcher, shortcut, or wizard unless the user asked for one.
- Use the least mechanism that satisfies the outcome. Prefer, in order: direct Agent instruction → project instruction → explicit command → lifecycle hook. A hook is not a more professional version of a sentence.
- Inspect authority before producing. Read the current user request, then project instructions, onboarding/runbooks, manifests, lockfiles, and actual command output. Do not make ONBOARDING.md, Python, uv, ffmpeg, or .env mandatory for repositories that do not declare them.
- Preserve user work. Never auto-stash, merge, rebase, force, discard, or overwrite local changes to make setup look successful.
- Define a falsifiable success state. "Dependencies installed" is not enough; run the project's real smoke test or startup command and verify the observable result.
- Keep diagnosis read-only until the cause is known. Installation, config edits, hook registration, commits, and external writes require the authority implied by the user's request; destructive or public actions require explicit approval.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 2.7 KB
- references/git_safety.md 3.9 KB
- references/onboarding_template.md 3.0 KB
- references/pii_guard.md 2.1 KB
- references/startup_automation.md 7.1 KB
- scripts/check_env.py 9.6 KB runs code
- scripts/init_session_start_hook.py 10 KB runs code
- scripts/sanitize_history.sh 3.9 KB runs code
- tests/test_scripts.py 9.6 KB runs code
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.
- 8d ago First seen · 236 lines · 112 tokens per session scan A 00a4c58d1d8d
auto-repo-setup is a skill published in the GitHub repository daymade/claude-code-skills (1,381 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,218 once invoked, about $0.0006 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-30.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.