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 agentmods add commands/christaylorcodes/github-template/customizegit clone --depth 1 https://github.com/christaylorcodes/GitHub-TemplateWhat 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 | $0.00007 | $0.00756 |
| Opus 5 | $0.00003 | $0.00378 |
| Sonnet 5 | $0.00001 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
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 yesterday.
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 — 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
-WhatIfto 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.mdandCODE_OF_CONDUCT.md-- do they still sayyourdomain.com?CONTRIBUTING.md-- does the title still reference the template?CHANGELOG.md-- does it still have template version history?README.mdbadge 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:
- README.md -- Rewrite the description, tagline, and getting-started sections for the actual project. Keep the structure but replace template marketing copy.
- CONTRIBUTING.md -- Update or remove Slack links. Ensure the title reflects this project.
- Contact emails -- Ask for real email addresses to replace
yourdomain.comin SECURITY.md and CODE_OF_CONDUCT.md. - Badges -- Update badge URLs once the user confirms their CI/CD setup.
- 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:
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.
- yesterday First seen · 74 lines · 7 tokens per session scan A caacf9b6859d
customize is a command published in the GitHub repository christaylorcodes/GitHub-Template (2 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 756 once invoked, about $0.0000 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.