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-discussion-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-discussion-replier)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/gh-discussion-replier"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/gh-discussion-replier/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/fu-jie/openwebui-extensions/gh-discussion-replier"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/gh-discussion-replier.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01169 |
| Opus 5 | $0.00023 | $0.00584 |
| Sonnet 5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
gh-discussion-replier scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
r = subprocess.run(['gh', 'api', 'graphql', How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gh Discussion Replier
Overview
The gh-discussion-replier skill enables posting professional English replies to GitHub Discussions. Unlike issues, discussions use the GraphQL API for both reading and posting. This skill handles the full workflow: fetching context, checking star status, composing a reply, and posting.
Workflow
- Identify the Discussion: Get the discussion number (e.g., #66) and URL.
- Fetch Discussion Content: Use GraphQL to get the title, body, author, and category.
- Check Star Status: Run the bundled script to check if the author has starred the repo.
- Command:
bash .github/skills/gh-discussion-replier/scripts/check_discussion_star.sh <discussion_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 references/templates.md to choose a suitable response pattern based on the discussion category (Ideas, Q&A, General, Show and tell).
- Draft the Reply: Compose a concise message based on star status and template.
- Post the Comment: Use the GraphQL
addDiscussionCommentmutation (see below).
Tool Integration
Fetch Discussion Content
import subprocess, json
def get_discussion(owner, repo, number):
query = '''
query($owner:String!, $repo:String!, $number:Int!) {
repository(owner:$owner, name:$repo) {
discussion(number:$number) {
id title body
author { login }
category { name }
comments(first:10) { nodes { body author { login } } }
}
}
}
'''
r = subprocess.run(['gh', 'api', 'graphql',
'-f', f'query={query}',
'-f', f'owner={owner}',
'-f', f'repo={repo}',
'-f', f'number={number}'],
capture_output=True, text=True)
return json.loads(r.stdout)['data']['repository']['discussion']
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.
- 10d ago First seen · 128 lines · 45 tokens per session scan A 1dc4a8152a90
gh-discussion-replier is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (307 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 1,169 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
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.
daily-logs
Track daily activity logs and summaries for the user. TRIGGER BY: read/edit user memory.
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
project-context
Use PowerContext project memory and handoff tools through MCP when continuing prior work, recalling decisions, maintaining durable memory, or transferring work across tasks, sessions, or agents.