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 Volchunovich/gum --skill gum-editgit clone --depth 1 https://github.com/Volchunovich/gumWrote 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/volchunovich/gum/gum-edit)<a href="https://agentmods.dev/skills/volchunovich/gum/gum-edit"><img src="https://agentmods.dev/badge/skills/volchunovich/gum/gum-edit/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/volchunovich/gum/gum-edit"><img src="https://agentmods.dev/badge/skills/volchunovich/gum/gum-edit.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.00017 | $0.02175 |
| Opus 5 | $0.00009 | $0.01087 |
| Sonnet 5 | $0.00003 | $0.00435 |
| Haiku 4.5 | $0.00002 | $0.00217 |
Grade A, and why
gum-edit 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit GUM Module
This skill modifies an existing GUM module. You read the module's current state, present it clearly, discuss changes with the user, update files, and resync hooks if needed. The user should always see what exists before deciding what to change.
Announce at start: "I'm using the gum-edit skill to modify an existing GUM module."
Checklist
IMMEDIATELY on skill load — before asking ANY question or producing ANY output other than the announcement — create a TaskCreate for EACH of these items:
- Read registry — find all available modules
- Select module — ask user which module to edit (or detect from context)
- Show current state — display rules.md, hooks.json, module.yaml
- Discuss changes — ask what the user wants to modify
- Update files — apply changes to rules.md, hooks.json, or module.yaml
- Resync hooks — if hooks.json changed, sync to runtime settings
- Confirm changes — show what was updated
Mark each task as completed as you finish it. Do NOT batch — mark done immediately.
The Iron Law
SHOW BEFORE YOU CHANGE. ALWAYS.
Never ask "what do you want to change?" without first showing the user exactly what the module contains right now. Context before questions.
When to Use
- User says "edit module", "update my gum module", "change the rules in X"
- User wants to add, remove, or modify rules in an existing module
- User wants to add or change hooks in a module
- User wants to enable/disable a module or change its metadata
- User realizes a rule should be a hook (or vice versa)
Use this ESPECIALLY when:
- User says "that rule isn't working" -- may need rule-to-hook promotion
- User wants to tweak hook behavior (different event, different tools)
- Module has grown stale and needs cleanup
Process
Phase 1: Find the Module
- Run
npx get-gum listvia Bash to get the list of all modules - If user specified a module name, locate it. If not found, show available modules and ask.
- If user didn't specify, show the list and ask which one to edit:
"Which module do you want to edit? Here are your modules:
enforce-tdd— Enforce test-driven development workflowauto-lint— Run eslint after file editsteam-standards— Team coding standards"
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.
- 10d ago First seen · 218 lines · 17 tokens per session scan A df773429d043
gum-edit is a skill published in the GitHub repository Volchunovich/gum (5 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 2,175 once invoked, about $0.0001 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…