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 Fu-Jie/openwebui-extensions --skill gh-issue-repliergit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWrote 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/fu-jie/openwebui-extensions/gh-issue-replier)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/gh-issue-replier"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/gh-issue-replier.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00509 |
| Opus 5 | $0.00023 | $0.00254 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
gh-issue-replier 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 8d 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.
What it actually says
Gh Issue Replier
Overview
The gh-issue-replier skill enables Gemini CLI to interact with GitHub issues professionally. It enforces English for all communications and leverages the gh CLI to post comments.
Workflow
- Identify the Issue: Find the issue number (e.g., #49).
- Check Star Status: Run the bundled script to check if the author has starred the repo.
- Command:
bash scripts/check_star.sh <issue-number> - Interpretation:
- Exit code 0: User has starred. Use "Already Starred" templates.
- Exit code 1: User has NOT starred. Include "Star Request" in the reply.
- Command:
- Select a Template: Load templates.md to choose a suitable English response pattern.
- Draft the Reply: Compose a concise message based on the star status.
- Post the Comment: Use the
ghtool to submit the reply.
Tool Integration
Check Star Status
bash scripts/check_star.sh <issue-number>
Post Comment
gh issue comment <issue-number> --body "<message-body>"
Example (if user has NOT starred):
gh issue comment 49 --body "This has been fixed in v1.2.7. If you find this helpful, a star on the repo would be much appreciated! ⭐"
Example (if user HAS starred):
gh issue comment 49 --body "This has been fixed in v1.2.7. Thanks for your support!"
Guidelines
- Language: ALWAYS use English for the comment body, even if the system prompt or user conversation is in another language.
- Tone: Professional, helpful, and appreciative.
- Precision: When announcing a fix, mention the specific version or the logic change (e.g., "Updated regex pattern").
- Closing: If the issue is resolved and you have permission, you can also use
gh issue close <number>.
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.
- 8d ago First seen · 52 lines · 47 tokens per session scan A f6b334ad8cf8
gh-issue-replier is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (305 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 509 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
timeline
Read back your append-only activity timeline for this repo+branch — a chronological log of session notes, context captures, and journal entries. Shows recent activity (last few days) by default, with the past-week view and the full all-time scroll alongside. Pass --rebuild to force a fresh rollup now. Use when the…
commit
Creates conventional git commits enriched with a Context section that logs AI-layer changes (.wisci/, CLAUDE.md, skills, rules), turning git history into queryable long-term memory. Use to commit changes, optionally pushing afterward.
project-memory
GitHub-native persistence for project learnings, decisions, and patterns using issue labels and structured comments. Used when recording what worked, what failed, or architectural decisions that should persist across sessions.
gsd-undo
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
user-general-facts
Capture and organize general facts about the user by topic.