agentmods.dev

gitea-comment-issue

gitea-comment-issue is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 122 tokens per session (550 once invoked), scanned A, original, MIT.

A workflow for posting a new comment on a Gitea issue or pull request. Gitea is a Git hosting service with issue and code-review discussions.

In plain words
What is it for?
Adding a contextual, evidence-based Markdown comment to a specified Gitea issue or pull request.
Why use it?
It confirms the target and checks the latest discussion before adding a comment, reducing the risk of posting to the wrong issue or repeating outdated information. It verifies that the comment was added.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 1repo changed 1mo ago A scan 122 tokens original MIT

Good fit Adding a contextual, evidence-based Markdown comment to a specified Gitea issue or pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-comment-issue
View source ↗ amonstack/gitea_mcp
Install

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.

Any agent
npx skills add amonstack/gitea_mcp --skill gitea-comment-issue
Clone the repo
git clone --depth 1 https://github.com/amonstack/gitea_mcp

Made for: Claude Code, Codex.

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 gitea-comment-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-comment-issue/github.svg)](https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-comment-issue)
Your own site
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-comment-issue"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-comment-issue/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 gitea-comment-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-comment-issue"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-comment-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 550 The whole file, excluding the scripts and references it only reads on demand.
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.00122 $0.00550
Opus 5.5 $0.00049 $0.00220
Sonnet 5.5 $0.00024 $0.00110
Haiku 4.5 $0.00012 $0.00055

Measured 1mo ago against content hash 0eb4e21c480e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitea-comment-issue 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 1mo 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.

src/assets/skills/gitea-comment-issue/SKILL.md · 39 lines

What it actually says

gitea-comment-issue

When to use

Trigger when the user asks to comment / reply / leave a note on an issue or PR — 中文请求如「在这个 issue 下评论一下」「回复这条 PR」「补充一句说明」也 MUST 走本 skill：先确认 issue 存在再发帖。

Post one new comment that advances an issue's discussion. Tools: get_issue, create_comment.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo). Never guess — wrong values post to the wrong place.
  • index = the issue number (URL #N → N), never the internal id.

Flow

  1. CONFIRM TARGET: get_issue({ index }) — verify the issue exists and is the one you mean. Do NOT post blind.
  2. POST: create_comment({ index, body }).

create_comment

  • RULES: body required, Markdown. The comment APPENDS to the thread — it never edits or replaces prior content. The response carries the comment id; retain it only if a follow-up update_comment / delete_comment is planned.
  • CHECK FIRST: re-read the latest thread (gitea-summarize-issue) so your comment is not redundant or contradicting a newer message.
  • CHECK AFTER: the comment appears with the returned id.

Body template — standardize what you write into body

A useful comment is contextual, evidence-backed, and proposes a next step. Structure body with this template; drop sections that add nothing.

**Context:** <the point you are responding to>

**Finding / proposal:** <what you discovered or suggest>

**Evidence:** <log excerpt, link, reproduction, or metric>

**Suggested next step:** <the concrete action you propose>
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. 1mo ago Changed · +4 lines · +32 tokens per session 0eb4e21c480e
  2. 1mo ago First seen · 35 lines · 90 tokens per session scan A 6dfe74647b2a

Subscribe to this mod's changes

gitea-comment-issue is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 21d ago), licensed MIT. It adds 122 tokens to every session and 550 once invoked, about $0.0005 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-08-31.

Git and workflowProject management
Related

Other skills, from other repositories

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens

implement-issue

Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.

CopilotKit/OpenTag · 35 tokens