agentmods.dev

reference-pack

A reference skillpack that demonstrates how third-party GBrain skillpacks are organised and checked. A skillpack is a bundle of agent instructions, tests, metadata, and operating guides.

In plain words
What is it for?
Learning what files a skillpack contains, how agents are routed to skills, and how its manifest, tests, runbook, and changelog are evaluated.
Why use it?
It gives skill authors a concrete structure to follow and explains the checks needed before a pack can be published.

Skill for Claude CodeCodex

29k +124 today A scan 31 tokens original MIT
View the source file garrytan/gbrain
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 skills/garrytan/gbrain/reference-pack
Any agent
npx skills add garrytan/gbrain --skill reference-pack
Clone the repo
git clone --depth 1 https://github.com/garrytan/gbrain

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,013 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.00031 $0.01013
Opus 5 $0.00015 $0.00507
Sonnet 5 $0.00006 $0.00203
Haiku 4.5 $0.00003 $0.00101

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

Security

Grade A, and why

reference-pack 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

examples/skillpack-reference/skills/reference-pack/SKILL.md · 104 lines

How it starts

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

reference-pack

This is the canonical reference for a third-party gbrain skillpack. Read its tree once and you know how to author one.

What this skill does

When the user asks how third-party gbrain skillpacks work, this skill points them at the four artifacts every pack ships:

  • skillpack.json — declares pack metadata + which artifacts the doctor scores (skills, unit_tests, e2e_tests, llm_evals, routing_evals, runbooks, changelog).
  • skills/<name>/SKILL.md — frontmatter (name, description, mutating, triggers) plus markdown body. Agents route on triggers:; the body is the in-context instruction set.
  • runbooks/bootstrap.md — agent-readable post-scaffold steps. gbrain DISPLAYS this after scaffold lands; the agent walks per-step at its own discretion. No auto-executor (codex T1 supply-chain hardening).
  • CHANGELOG.md — Keep-a-Changelog shape. The doctor's changelog_ present_and_current dimension fails if there's no ## [<version>] entry matching the manifest's version.

What the doctor scores

Ten binary dimensions, split into:

Core (5; must all pass to publish at any tier):

  1. manifest_valid — schema-validates skillpack.json
  2. skills_have_skill_md — every listed skill has SKILL.md with name / description / triggers
  3. routing_evals_present — each skill has routing-eval.jsonl with

    = 5 intents

  4. skills_have_unique_triggers — MECE at the pack level
  5. changelog_present_and_current — CHANGELOG entry for current version

Quality badges (5; earn for tier eligibility):

  1. unit_tests_present — manifest.unit_tests matches >= 1 file
  2. e2e_tests_present — manifest.e2e_tests matches >= 1 file
  3. llm_eval_present — *.judge.json with >= 3 cases
  4. bootstrap_runbook_present — non-empty runbooks/bootstrap.md
  5. license_present — LICENSE / LICENSE.md / LICENSE.txt non-empty

Tier eligibility:

  • endorsed — all 10 (gates: Garry's endorsements.json overlay in the registry)
  • community — all 5 core + >= 3 of 5 badges (default tier on PR merge)
  • experimental — all 5 core + < 3 badges
  • blocked — any core fails

Read the full file on GitHub · 104 lines

Files

What ships with it

1 file 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.

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 · 104 lines · 31 tokens per session scan A e15a5cde2b58

Subscribe to this mod's changes

reference-pack is a skill published in the GitHub repository garrytan/gbrain (29,440 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,013 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens