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 skills add thettwe/nyann --skill gen-templatesgit clone --depth 1 https://github.com/thettwe/nyannWrote 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.
[](https://agentmods.dev/skills/thettwe/nyann/gen-templates)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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
- Resolve and load the active profile via
bin/load-profile.sh <name>(resolves preferences → CLAUDE.md markers →"default"fallback).
Phase 2: Preview
- Run
bin/gen-templates.sh --profile <profile> --target . --dry-runto preview. - 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
- Ask: "Write these templates to
.github/?" - On confirmation, run without
--dry-run. - If files already exist, mention
--forceto overwrite.
Phase 4: Suggest next steps
- Suggest:
- "Run
/nyann:gen-cito add a CI workflow" - "Commit and push to see templates on GitHub"
- "Run
Key constraints
- Existing template files are NOT overwritten unless
--forceis 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-ciskill. - "Apply branch protection" →
gh-protectskill. - "Commit these templates" →
commitskill.
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.
- 1mo ago First seen · 57 lines · 93 tokens per session scan A f535133b8dbe
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.
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…
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.
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).
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…
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…
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…