GitHub-Template: Command for Claude Code

.claude/commands/customize.md

customize is a command for Claude Code from christaylorcodes/GitHub-Template. It costs 7 tokens per session (756 once invoked), scanned A, original, MIT.

A guided command for replacing template-specific project details with the information for your own project.

In plain words
What is it for?
Use it to check initialization, provide project and author details, run the setup script, and review files such as the README, security policy, and contribution guide.
Why use it?
It helps find unfinished template placeholders and applies the documented initialization and customization steps.

Command for Claude Code

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

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./Tests/test-local.ps1.

Reuse

Borrowing it

Nothing to install: this file belongs to christaylorcodes/GitHub-Template. 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/christaylorcodes/GitHub-Template/main/.claude/commands/customize.md
Clone the repo
git clone --depth 1 https://github.com/christaylorcodes/GitHub-Template

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 customize

README.md
[![agentmods](https://agentmods.dev/badge/commands/christaylorcodes/github-template/customize/github.svg)](https://agentmods.dev/commands/christaylorcodes/github-template/customize)
Your own site
<a href="https://agentmods.dev/commands/christaylorcodes/github-template/customize"><img src="https://agentmods.dev/badge/commands/christaylorcodes/github-template/customize/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 customize

Your own site · 80×15
<a href="https://agentmods.dev/commands/christaylorcodes/github-template/customize"><img src="https://agentmods.dev/badge/commands/christaylorcodes/github-template/customize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 756 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.00007 $0.00756
Opus 5.5 $0.00003 $0.00302
Sonnet 5.5 $0.00001 $0.00151
Haiku 4.5 $0.00001 $0.00076

Measured 2mo ago against content hash caacf9b6859d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

customize 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 2mo 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/commands/customize.md · 74 lines

How it starts

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

You are helping the user customize their project after it was created from the GitHub Template. Read docs/CUSTOMIZATION_GUIDE.md (may still be named docs/AI_SETUP_GUIDE.md if the init script hasn't run yet) for the full reference.

Step 1: Check initialization status

Check whether Scripts/Initialize-Repository.ps1 still exists.

  • If it exists: The template hasn't been initialized yet. Gather the required information from the user (module name, description, author, GitHub username) and run the script first. Use -WhatIf to preview, then run for real. See section 1 of the customization guide for the full parameter list.
  • If it doesn't exist: Initialization is done. Proceed to customization.

Step 2: Assess current state

Read these files to understand what still needs customization:

  • README.md -- does the prose still describe the template?
  • SECURITY.md and CODE_OF_CONDUCT.md -- do they still say yourdomain.com?
  • CONTRIBUTING.md -- does the title still reference the template?
  • CHANGELOG.md -- does it still have template version history?
  • README.md badge URLs -- do they point to real CI/CD or placeholder URLs?

Tell the user what you found and what needs updating.

Step 3: Customize interactively

Work through each item that needs attention. Ask the user for input where needed:

  1. README.md -- Rewrite the description, tagline, and getting-started sections for the actual project. Keep the structure but replace template marketing copy.
  2. CONTRIBUTING.md -- Update or remove Slack links. Ensure the title reflects this project.
  3. Contact emails -- Ask for real email addresses to replace yourdomain.com in SECURITY.md and CODE_OF_CONDUCT.md.
  4. Badges -- Update badge URLs once the user confirms their CI/CD setup.
  5. CHANGELOG.md -- Write a meaningful first entry for this project.

Step 4: Adapt existing code (if applicable)

Ask the user if they have existing PowerShell code to bring into this project. If yes:

Read the full file on GitHub · 74 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. 2mo ago First seen · 74 lines · 7 tokens per session scan A caacf9b6859d

Subscribe to this mod's changes

customize is a command published in the GitHub repository christaylorcodes/GitHub-Template (2 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 756 once invoked, about $0.0000 per session on Opus 5.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

customize compared with commands from other repositories

customize next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
customizechristaylorcodes/GitHub-TemplateCommand24mo agoMITA7Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code