Umbraco.Automate: Skill for Claude Code

.claude/skills/repo-setup/SKILL.md

repo-setup is a skill for Claude Code from umbraco/Umbraco.Automate. It costs 42 tokens per session (546 once invoked), scanned A, original, MIT.

A repository setup procedure for the Umbraco.Automate project, an application built with .NET and JavaScript. It prepares development tools and optional demo content.

In plain words
What is it for?
Use it to install Git hooks, create a demo Umbraco site, install npm dependencies, and run the initial .NET build.
Why use it?
It reduces the manual work needed when a developer first joins the project or resets their local environment.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is umbraco/Umbraco.Automate's own configuration. It tells Claude Code how to work on Umbraco.Automate 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 Umbraco.Automate configures →

Reuse

Borrowing it

Nothing to install: this file belongs to umbraco/Umbraco.Automate. 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/umbraco/Umbraco.Automate/v18/dev/.claude/skills/repo-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/umbraco/Umbraco.Automate

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/umbraco/umbraco.automate/repo-setup"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/repo-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 546 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.
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.00042 $0.00546
Opus 5 $0.00021 $0.00273
Sonnet 5 $0.00008 $0.00109
Haiku 4.5 $0.00004 $0.00055

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

Security

Grade A, and why

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 10d 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.

.claude/skills/repo-setup/SKILL.md · 71 lines

What it actually says

Setup Repository

You are helping set up the Umbraco.Automate repository for local development.

Task

Perform initial repository setup by running the appropriate setup scripts based on the user's platform and preferences.

Available Setup Tasks

  1. Git Hooks - Install git hooks for branch naming enforcement

    • Windows: .\scripts\setup-git-hooks.ps1
    • Linux/Mac: ./scripts/setup-git-hooks.sh
  2. Demo Site - Create unified solution with demo Umbraco instance

    • Windows: .\scripts\install-demo-site.ps1
    • Linux/Mac: ./scripts/install-demo-site.sh
    • Options: -SkipTemplateInstall / -Force (PowerShell) or --skip-template-install / --force (Bash)
  3. Dependencies - Install npm workspace dependencies

    • Command: npm install
  4. Initial Build - Build the unified solution

    • Command: dotnet build Umbraco.Automate.local.slnx

Workflow

  1. Detect platform - Check if Windows (PowerShell) or Linux/Mac (Bash)
  2. Ask user what to set up - Use AskUserQuestion with options:
    • "Git hooks only"
    • "Git hooks + demo site"
    • "Full setup (hooks + demo + dependencies + build)"
    • Allow custom selections
  3. Execute selected tasks in order
  4. Report results - Show what was completed and any errors

Important Notes

  • Always run scripts from the repository root
  • Check if demo site already exists before running install script
  • Use platform-specific script extensions (.ps1 vs .sh)
  • Provide clear feedback after each step
  • If any step fails, report it but continue with remaining tasks if possible

Example Flow

User invokes: /repo-setup

You ask: "What would you like to set up?"
- Git hooks only
- Git hooks + demo site
- Full setup (hooks + demo + dependencies + build)

User selects: "Full setup"

You execute:
1. Run setup-git-hooks script
2. Run install-demo-site script
3. Run npm install
4. Run dotnet build

Report: "Setup complete!"
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. 10d ago First seen · 71 lines · 42 tokens per session scan A 01ae14cd914e

Subscribe to this mod's changes

repo-setup is a skill published in the GitHub repository umbraco/Umbraco.Automate (5 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 546 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens