agentmods.dev

gitea-summarize-issue

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

A procedure for reading and summarizing a Gitea issue and its comments. An issue is a project discussion used to track a problem, request, or decision.

In plain words
What is it for?
Use it to report the issue's state, original request, discussion consensus, disagreements, and unresolved questions, while warning if a long comment thread was truncated.
Why use it?
It gathers the issue details and discussion so the current decision, agreement, and unanswered questions are clear.

Skill for Claude CodeCodex

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

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

Good fit Use it to report the issue's state, original request, discussion consensus, disagreements, and unresolved questions, while warning if a long comment thread was truncated.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-summarize-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-summarize-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-summarize-issue

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-summarize-issue"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-summarize-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 412 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.00098 $0.00412
Opus 5.5 $0.00039 $0.00165
Sonnet 5.5 $0.00020 $0.00082
Haiku 4.5 $0.00010 $0.00041

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

Security

Grade A, and why

gitea-summarize-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-summarize-issue/SKILL.md · 26 lines

What it actually says

gitea-summarize-issue

When to use

Trigger when the user asks to summarize / digest an issue's discussion — 中文请求如「总结一下这个 issue」「这个 issue 讨论到哪了」也 MUST 走本 skill。

Read an issue and its discussion, then synthesize. Tools: get_issue, list_comments.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo).

Flow

  1. get_issue({ index }) — index = issue number (URL #N → N), never the internal id. The comments field is only a COUNT.
  2. list_comments({ index }) — returns the comment thread, oldest-first.

list_comments — TRUNCATION TRAP

  • This tool passes NO page/limit and returns at most the server's default page size. For long threads the list is SILENTLY TRUNCATED. If the comments count (from get_issue) exceeds the number returned, warn that part of the thread is missing and do NOT claim a complete summary.

Synthesis

  • Report the issue state (open/closed), the body's ask, then the thread's consensus / decision / open questions. Attribute by author. Flag unresolved disagreement explicitly — do not paper over it.
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 · +28 tokens per session f322325655fb
  2. 1mo ago First seen · 22 lines · 70 tokens per session scan A 3c8985690d08

Subscribe to this mod's changes

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

Project management
Related

Other skills, from other repositories

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens