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/saffron-health/opencode-gui/commitnpx skills add saffron-health/opencode-gui --skill commitgit clone --depth 1 https://github.com/saffron-health/opencode-guiWhat 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.00027 | $0.00742 |
| Opus 5 | $0.00014 | $0.00371 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
commit 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automatically stage all changes and commit with an appropriate message based on the changes made. Shows a summary of what files were changed and how.
Steps
-
Show current status before staging:
git status --porcelain -
Stage all changes:
git add . -
Get changed files for analysis:
git diff --cached --name-only -
Get detailed change summary:
git diff --cached --stat -
Analyze changes to create commit message:
- Read the changed files to understand the scope of changes
- Look for spec files in
specs/directory that might be related to these changes - Focus on the main functional changes rather than minor refactoring
- Create a concise, descriptive commit message following conventional commit format
- Consider these patterns:
feat: add new featurefix: resolve bug in componentrefactor: reorganize utility functionsdocs: update documentationchore: update dependencies
-
Commit the changes:
git commit -m "Generated commit message" -
Show commit summary:
git show --stat --oneline HEAD
Analysis Guidelines
Commit Message Format
- Use conventional commit format:
type: description - Keep it concise and descriptive
- Focus on what the change accomplishes, not how it was done
- Use imperative mood: "add" not "added"
Change Analysis Priority
- Spec files: New/modified files in
specs/indicate major features - Core functionality: API endpoints, UI components, database schemas
- Configuration: Build, dependency, or environment changes
- Documentation: README, AGENT.md, or other doc updates
- Refactoring: Code reorganization without functional changes
Example Output
Files staged for commit:
M apps/web/src/components/TaskList.tsx
A specs/task-filters.md
M packages/ui/src/Button.tsx
D apps/web/src/old-component.tsx
Changes summary:
apps/web/src/components/TaskList.tsx | 15 ++++++++++++---
specs/task-filters.md | 42 +++++++++++++++++++++++++++++++++++++++
packages/ui/src/Button.tsx | 8 ++++----
apps/web/src/old-component.tsx | 23 -----------------------
4 files changed, 58 insertions(+), 26 deletions(-)
Committed: feat: add task filtering functionality
[main abc1234] feat: add task filtering functionality
4 files changed, 58 insertions(+), 26 deletions(-)
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 · 111 lines · 27 tokens per session scan A 39233a6008f6
commit is a skill published in the GitHub repository saffron-health/opencode-gui (57 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 742 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-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…