What is GitHub-Template?

A settings file allows one specific GitHub command: creating an issue for committing v1.1 changes, checking CI, and tagging the release. CI means automated checks that run when code changes.

Use it to create the documented GitHub release issue with its objective, requirements, context, and acceptance criteria.

It limits the agent’s allowed tool use to that predefined release-tracking action.

How christaylorcodes/GitHub-Template configures Claude Code

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/settings.json

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.

README.md

[![agentmods](https://agentmods.dev/badge/settings/christaylorcodes/github-template/settings/github.svg)](https://agentmods.dev/settings/christaylorcodes/github-template/settings)

Your own site

<a href="https://agentmods.dev/settings/christaylorcodes/github-template/settings"><img src="https://agentmods.dev/badge/settings/christaylorcodes/github-template/settings/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.

Your own site · 80×15

<a href="https://agentmods.dev/settings/christaylorcodes/github-template/settings"><img src="https://agentmods.dev/badge/settings/christaylorcodes/github-template/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

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.

Security

Grade A, and why

GitHub-Template 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/settings.json · 8 lines

What it actually says

{
  "permissions": {
    "allow": [
      "Bash(\"$GH\" issue create --title \"Commit v1.1 changes, verify CI, tag release\" --body \"$\\(cat <<''EOF''\n## Objective\n\nCommit all v1.1 changes, push to GitHub, verify CI workflows pass, and tag the v1.1 release.\n\n## Requirements\n\n- [ ] Stage and commit all changes\n- [ ] Push and verify CI workflows pass \\(test.yml, analyze.yml\\)\n- [ ] Tag v1.1 release\n\n## Context\n\nv1.1 removed legacy Sampler/ModuleBuilder tooling, consolidated on InvokeBuild, added full module template structure, and cleaned up repo layout. Local validation passes: 18/18 tests, 93.1% coverage, 0 analyzer errors.\n\n## Acceptance Criteria\n\n- All CI checks pass on both Ubuntu and Windows\n- v1.1 tag exists on the commit\nEOF\n\\)\" --milestone \"v1.1 Release\" --label \"ai-task,ai-ready\")"
    ]
  }
}

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.

2mo ago First seen · 8 lines scan A 9423fe8eff47

Subscribe to this mod's changes

GitHub-Template is a settings file published in the GitHub repository christaylorcodes/GitHub-Template (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

CI and CD DevOps and cloud Git and workflow Releases

GitHub-Template next to 6 settings from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
GitHub-Templatechristaylorcodes/GitHub-Template	Settings file	2	4mo ago	MIT	A	—	Claude Code
supabasesupabase/supabase	Settings file	115k	yesterday	Apache-2.0	A	—	Claude Code
supersetapache/superset	Settings file	75k	today	Apache-2.0	A	—	Claude Code
RuViewruvnet/RuView	Settings file	103k	yesterday	MIT	A	—	Claude Code
claude-cookbooksanthropics/claude-cookbooks	Settings file	54k	2d ago	MIT	A	—	Claude Code
ormprisma/orm	Settings file	48k	yesterday	Apache-2.0	A	—	Claude Code
claude-code-best-practiceshanraisshan/claude-code-best-practice	Settings file	69k	yesterday	MIT	A	—	Claude Code

GitHub-Template: Settings file for Claude Code