gen-templates

gen-templates is a skill for Claude Code from thettwe/nyann. It costs 93 tokens per session (538 once invoked), scanned A, original, MIT.

A generator for GitHub pull-request and issue templates. These templates give contributors standard forms and checklists for reviewing changes, reporting bugs, and requesting features.

In plain words
What is it for?
Use it to create a pull-request template, bug-report template, feature-request template, and related GitHub configuration in .github/.
Why use it?
It makes repository contributions more consistent and reminds authors of the project’s required quality checks before review.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md.

Part of the nyann plugin — 41 skills, 41 commands, 3 hooks shipped together

Good fit Use it to create a pull-request template, bug-report template, feature-request template, and related GitHub configuration in .github/.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thettwe/nyann/gen-templates
Install

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.

Any agent
npx skills add thettwe/nyann --skill gen-templates
Clone the repo
git clone --depth 1 https://github.com/thettwe/nyann

Made for: Claude Code.

Or install nyann, the plugin that ships this one along with the rest of its 41 skills, 41 commands, 3 hooks.

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 gen-templates

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/thettwe/nyann/gen-templates"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/gen-templates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 538 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.00093 $0.00538
Opus 5.5 $0.00037 $0.00215
Sonnet 5.5 $0.00019 $0.00108
Haiku 4.5 $0.00009 $0.00054

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

Security

Grade A, and why

gen-templates 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 1mo 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.

skills/gen-templates/SKILL.md · 57 lines

What it actually says

gen-templates — Generate GitHub PR and Issue Templates

You are the gen-templates skill. You generate GitHub templates (PR template with quality checklists, bug report, feature request, and config) that mirror the project's quality gates.

When to trigger

  • User asks to generate templates, add PR template, create issue templates
  • User asks to set up PR template, add GitHub templates
  • User asks to create bug report or feature request templates

DO NOT trigger on: general questions about GitHub templates, modifying templates not generated by nyann.

Execution flow

Phase 1: Resolve profile

  1. Resolve and load the active profile via bin/load-profile.sh <name> (resolves preferences → CLAUDE.md markers → "default" fallback).

Phase 2: Preview

  1. Run bin/gen-templates.sh --profile <profile> --target . --dry-run to preview.
  2. Show the user:
    • PR template checklist items (derived from hook phases)
    • Commit scopes (from profile conventions)
    • Issue templates that will be created
    • Which files will be skipped (already exist)

Phase 3: Confirm and write

  1. Ask: "Write these templates to .github/?"
  2. On confirmation, run without --dry-run.
  3. If files already exist, mention --force to overwrite.

Phase 4: Suggest next steps

  1. Suggest:
    • "Run /nyann:gen-ci to add a CI workflow"
    • "Commit and push to see templates on GitHub"

Key constraints

  • Existing template files are NOT overwritten unless --force is passed. This respects user customizations.
  • If the profile has no hooks, a minimal default checklist is generated.
  • Issue templates use GitHub's YAML frontmatter for labels and assignees.

When to hand off

  • "Add a CI workflow too" → gen-ci skill.
  • "Apply branch protection" → gh-protect skill.
  • "Commit these templates" → commit skill.
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. 1mo ago First seen · 57 lines · 93 tokens per session scan A f535133b8dbe

Subscribe to this mod's changes

gen-templates is a skill published in the GitHub repository thettwe/nyann (7 stars, last pushed 6d ago), licensed MIT. It adds 93 tokens to every session and 538 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

daily-working

End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…

tms-tungnguyen3/daily_working · 98 tokens

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

phx-deps-update

Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).

oliver-kriska/claude-elixir-phoenix · 62 tokens

chief-operating-officer

Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…

cbrock84/headcount · 0 tokens

chief-product-officer

Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…

cbrock84/headcount · 0 tokens

customer-success-management

Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…

cbrock84/headcount · 85 tokens