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 agentmods add skills/addono/gh-attach/probot-settingsnpx skills add Addono/gh-attach --skill probot-settingsgit clone --depth 1 https://github.com/Addono/gh-attachWhat 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 | $0.00066 | $0.00806 |
| Opus 5 | $0.00033 | $0.00403 |
| Sonnet 5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
probot-settings 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Probot Settings
Use this skill when a repository needs a new or updated .github/settings.yml managed by the
Repository Settings GitHub App (repository-settings/app) or the older Probot Settings docs.
Step 0 — Determine Scope
Default to the current repository unless the user explicitly names another one.
gh repo view --json nameWithOwner -q .nameWithOwner
# Fallback:
git remote get-url origin
Step 1 — Gather the Current State
If .github/settings.yml already exists, read it first and update it surgically.
If the file does not exist yet, inspect the live repository and current labels:
REPO=<owner/repo>
gh repo view "$REPO" --json \
name,nameWithOwner,description,homepageUrl,isPrivate,hasIssuesEnabled,hasWikiEnabled,defaultBranchRef,mergeCommitAllowed,rebaseMergeAllowed,squashMergeAllowed,deleteBranchOnMerge,repositoryTopics
gh label list --repo "$REPO" --json name,color,description --limit 200
Only inspect advanced sections when you actually plan to manage them:
- Branch protection:
gh api repos/$REPO/branches/<branch>/protection - Environments:
gh api repos/$REPO/environments - Teams / collaborators: inspect only for organisation-owned repositories
See references/sections-and-gotchas.md for section-level guidance.
Step 2 — Build the File from Minimal to Specific
Prefer a small, accurate file over a giant aspirational one.
- Start with
repository:and preserve the real repo name, description, homepage, visibility, default branch, and merge strategy. - Add
labels:next; preserve existing labels unless the user wants a deliberate cleanup. - Add
teams,collaborators,branches,environments, ormilestonesonly when the repo already uses them or the user explicitly asks for them. - Keep comments short and useful; follow the existing file style if one already exists.
Use references/addono-examples.md for Addono-flavoured patterns and example repos.
Step 3 — Encode Important Upstream Rules
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 93 lines · 66 tokens per session scan A 685ed618e900
probot-settings is a skill published in the GitHub repository Addono/gh-attach (3 stars, last pushed 20d ago), licensed MIT. It adds 66 tokens to every session and 806 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.