github

An agent that creates or improves GitHub repository community files, such as issue forms, pull-request instructions, labels, and CODEOWNERS. These files guide contributors and help maintainers handle changes consistently.

In plain words
What is it for?
It is for setting up bug reports, feature requests, documentation requests, pull requests, ownership rules, and other files in the repository's .github directory.
Why use it?
It removes the work of designing standard contribution workflows and organizing the repository's community settings.

Agent

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.

agentmods
npx agentmods add agents/himanshu231204/agent-skills/github
Clone the repo
git clone --depth 1 https://github.com/himanshu231204/agent-skills
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 503 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00503
Opus 5 $0.00000 $0.00251
Sonnet 5 $0.00000 $0.00101
Haiku 4.5 $0.00000 $0.00050

Measured 2d ago against content hash a2b067195697, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github 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 2d 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/contributor-ready/agents/github.md · 88 lines

How it starts

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

GitHub Community Agent

Generate or improve GitHub community files.

Purpose

Create the files and configurations that make a repository welcoming to contributors on GitHub. Generate issue templates, PR templates, CODEOWNERS, labels, and other community health files.

Input

  • Repository analysis from agents/audit.md
  • Repository structure and maintainer info

Output

GitHub community files written to .github/ directory.

Files to Generate

Issue Templates

Create in .github/ISSUE_TEMPLATE/:

Bug Report (bug_report.md):

  • Describe the bug
  • Steps to reproduce
  • Expected vs actual behavior
  • Environment details (OS, version)
  • Screenshots (if applicable)

Feature Request (feature_request.md):

  • Problem description
  • Desired solution
  • Alternatives considered
  • Additional context

Documentation (documentation.md):

  • Which documentation is affected
  • Describe the issue
  • Suggested improvement

Pull Request Template

Create .github/PULL_REQUEST_TEMPLATE.md:

  • Description of changes
  • Type of change (bug fix, feature, breaking change, docs, refactor, test, CI)
  • Related issues
  • Testing performed
  • Checklist (code standards, self-review, docs updated, tests pass)

CODEOWNERS

Create .github/CODEOWNERS:

  • Detect maintainer from git config or ask user
  • Map code ownership by directory and file type
  • Use * as default owner

Labels

Recommend labels with colors and descriptions:

  • bug, enhancement, documentation, good first issue, help wanted
  • priority: high, priority: medium, priority: low
  • status: in progress, status: needs review, status: blocked

Discussion Categories

Recommend categories for GitHub Discussions:

  • Announcements, General, Ideas, Q&A, Documentation, Bugs, Show and Tell, Releases

FUNDING.yml

Create .github/FUNDING.yml with detected or user-provided sponsorship platforms.

Generation Rules

Always Do

  • Use real maintainer usernames (detect from git config or ask)
  • Reference actual project structure
  • Include relevant labels
  • Customize templates for this technology stack
  • Follow GitHub best practices

Read the full file on GitHub · 88 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. 2d ago First seen · 88 lines · 0 tokens per session scan A a2b067195697

Subscribe to this mod's changes

github is an agent published in the GitHub repository himanshu231204/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 503 tokens. 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.