openwebui-extensions: Instructions file for Kiro

.kiro/steering/gh-issue-replier.md

gh-issue-replier is an instructions file for Kiro from Fu-Jie/openwebui-extensions. It costs 527 tokens per session, scanned A, original, MIT.

A GitHub issue reply helper that drafts and posts professional English comments with the GitHub command-line tool. It checks whether the issue author has starred the repository so the reply can use the matching template.

In plain words
What is it for?
Use it to reply when a bug is fixed, a task is complete, or a maintainer needs details from the reporter. It can check the issue and submit the comment.
Why use it?
It removes the repetitive work of checking issue status, choosing a response, and posting it by hand. It also keeps replies consistent after a fix or when more information is needed.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Fu-Jie/openwebui-extensions's own configuration. It tells Kiro how to work on openwebui-extensions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openwebui-extensions configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash .agent/skills/gh-issue-replier/scripts/check_star.sh <issue-number>.

Reuse

Borrowing it

Nothing to install: this file belongs to Fu-Jie/openwebui-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Fu-Jie/openwebui-extensions/main/.kiro/steering/gh-issue-replier.md
Clone the repo
git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

Made for: Kiro.

Wrote 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.

agentmods badge for gh-issue-replier

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/gh-issue-replier/github.svg)](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/gh-issue-replier)
Your own site
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/gh-issue-replier"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/gh-issue-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.

agentmods 80×15 button for gh-issue-replier

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/gh-issue-replier"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/gh-issue-replier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 527 This file is loaded in full into every session.
When invoked 527 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00527 $0.00527
Opus 5.5 $0.00211 $0.00211
Sonnet 5.5 $0.00105 $0.00105
Haiku 4.5 $0.00053 $0.00053

Measured 26d ago against content hash 686dd85ccc23, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 26d 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.

.kiro/steering/gh-issue-replier.md · 53 lines

What it actually says

Gh Issue Replier

Overview

The gh-issue-replier skill enables the agent to interact with GitHub issues professionally. It enforces English for all communications and leverages the gh CLI to post comments.

Workflow

  1. Identify the Issue: Find the issue number (e.g., #49).
  2. Check Star Status: Run the bundled script to check if the author has starred the repo.
    • Command: bash .agent/skills/gh-issue-replier/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.
  3. Select a Template: Load templates to choose a suitable English response pattern.
  4. Draft the Reply: Compose a concise message based on the star status.
  5. Post the Comment: Use the gh tool to submit the reply.

Tool Integration

Check Star Status

bash .agent/skills/gh-issue-replier/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>.
Changes

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.

  1. 26d ago First seen · 53 lines · 527 tokens per session scan A 686dd85ccc23

Subscribe to this mod's changes

gh-issue-replier is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (333 stars, last pushed 27d ago), licensed MIT. It adds 527 tokens to every session, about $0.0021 per session on Opus 5.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-10-11.

Related

gh-issue-replier compared with instructions from other repositories

gh-issue-replier next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
gh-issue-replierFu-Jie/openwebui-extensionsInstructions file33327d agoMITA527Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode