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/markerikson/opencode-config-example/gittonpx skills add markerikson/opencode-config-example --skill gittogit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00034 | $0.00605 |
| Opus 5 | $0.00017 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
gitto 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitto - GitHub Bug Pattern Search
Purpose
Turn a bug description into targeted GitHub code and issue searches, then summarize patterns and candidate fixes.
When to Use
- Investigating a bug and want to see how others solved similar issues
- Looking for code patterns or examples from public repositories
- The user provides a problem statement but no specific repo to inspect
- Redux/RTK issue triage - finding related issues or prior art
Inputs
- Bug description (required)
- Optional: language, framework, error strings, org/repo constraints, result limit
Process
- Extract key phrases, error strings, and likely library/framework terms from the bug description
- Build 2-4 query variants with GitHub code search qualifiers
- Run searches using the gitto script (uses
ghCLI if authenticated, falls back to API) - Rank results by relevance and return URLs with snippets
- Provide analysis: summarize patterns, likely root causes, and 2-3 candidate fixes
Command
bun ~/.config/opencode/skill/gitto/gitto-search.ts \
--query "<bug description or keywords>" \
--language "typescript" \
--limit 15 \
--issues true
Options
--query(required): Bug description or search keywords--language: Filter by language (e.g., "typescript", "javascript")--repo: Specific repo (e.g., "reduxjs/redux-toolkit")--org: Organization filter--limit: Max results (default: 20)--issues: Include issue search (default: true)
Output Format
- Code results: Repo, file path, URL, snippet
- Issue results: Title, URL, body snippet
- Use results to provide analysis of patterns and candidate fixes
Example Usage
For Redux middleware issues:
bun ~/.config/opencode/skill/gitto/gitto-search.ts \
--query "middleware dispatch undefined action" \
--org "reduxjs" \
--language "typescript" \
--limit 10
For React hooks errors:
bun ~/.config/opencode/skill/gitto/gitto-search.ts \
--query "useEffect cleanup memory leak" \
--language "typescript" \
--issues true
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.
- 2d ago First seen · 77 lines · 34 tokens per session scan A 30658c81ea82
gitto is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 605 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…