skill-doctor github-automation.instructions.md

Instructions for automating GitHub, a service for hosting and collaborating on code. They cover common repository tasks such as branches, commits, pull requests, issues, and releases.

In plain words
What is it for?
They help create branches and commits, open pull requests, prepare releases, and update issue labels.
Why use it?
They give code changes a focused workflow and require the work and verification steps to be summarized clearly.

Instructions file for GitHub Copilot

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 instructions/evilstar2016/skill-doctor/github-automation
Clone the repo
git clone --depth 1 https://github.com/evilstar2016/skill-doctor

Made for: GitHub Copilot.

Per session 72 This file is loaded in full into every session.
When invoked 72 The same file — it is already loaded in full.
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.00072 $0.00072
Opus 5 $0.00036 $0.00036
Sonnet 5 $0.00014 $0.00014
Haiku 4.5 $0.00007 $0.00007

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

Security

Grade A, and why

skill-doctor github-automation.instructions.md 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.

examples/conflicted-agent-project/.github/instructions/github-automation.instructions.md · 22 lines

What it actually says

github-automation

Description

Automates GitHub branch, commit, pull request, issue, and release workflows.

When to Use

  • create branch
  • write commit
  • open pull request
  • prepare release
  • update issue labels

Instructions

Keep repository changes focused and summarize verification steps.

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 · 22 lines · 72 tokens per session scan A ccf3f28a8e12

Subscribe to this mod's changes

skill-doctor github-automation.instructions.md is an instructions file published in the GitHub repository evilstar2016/skill-doctor (7 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session, about $0.0004 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.