agentmods.dev

gitea-find-issues

gitea-find-issues is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 124 tokens per session (645 once invoked), scanned A, original, MIT.

A read-only tool for discovering and reading issues in Gitea, a self-hosted Git service. It can list issues in one repository, search issues across repositories, or read one issue in detail.

In plain words
What is it for?
Use it to list repository issues, search for issue keywords across repositories, inspect a specific issue, and distinguish pull requests included in issue results.
Why use it?
It helps locate and triage existing issues without accidentally changing, closing, or deleting them.

Skill for Claude CodeCodex

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

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

Good fit Use it to list repository issues, search for issue keywords across repositories, inspect a specific issue, and distinguish pull requests included in issue results.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-find-issues"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-find-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 645 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.00124 $0.00645
Opus 5.5 $0.00050 $0.00258
Sonnet 5.5 $0.00025 $0.00129
Haiku 4.5 $0.00012 $0.00064

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

Security

Grade A, and why

gitea-find-issues 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-find-issues/SKILL.md · 36 lines

What it actually says

gitea-find-issues

When to use

Trigger when the user asks to list / search / find / read issues — 中文请求如「看看有哪些 issue」「搜一下关于 X 的问题」「这个 issue 讲了什么」也 MUST 走本 skill。

Read-only issue discovery. Tools: list_issues, search_issues, get_issue.

Prerequisites

  • Resolve owner+repo for list_issues/get_issue: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo). Never guess — wrong values 404 or silently target the wrong repo.
  • Paginate 1-based, limit ≤ 100. A page is final ONLY when it returns fewer than limit items. Always set limit (default page size is server-controlled).

Choose the tool

  • ONE repo's issues, filtered by state/labels → list_issues.
  • ACROSS repos by keyword, or duplicate check → search_issues (global; no owner/repo).
  • ONE issue's full detail → get_issue.

list_issues

  • RULES: labels = comma-separated NAMES, AND-matched; a mistyped or non-existent name returns EMPTY with no error. Results include pull requests (no type filter here); identify a PR by a non-null pull_request field in the JSON.
  • CHECK FIRST: confirm label names via list_labels (gitea-manage-labels) before filtering.
  • CHECK AFTER: if length === limit, fetch the next page before treating the list as complete.

search_issues

  • RULES: GLOBAL — no owner/repo; each result carries its own repository. Returns issues AND PRs by default; set type: "issues" to exclude PRs (type: "pulls" for PRs only). labels = names. query matches title + body.
  • CHECK FIRST: set type deliberately.
  • CHECK AFTER: page fully if completeness matters.

get_issue

  • RULES: pass index = the issue number (URL #42 → 42), never the internal id.
  • NOTE: the comments field is a COUNT only — to read the discussion use list_comments (gitea-summarize-issue).
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 · +34 tokens per session c0d5d2bae365
  2. 1mo ago First seen · 32 lines · 90 tokens per session scan A 4978812b33ab

Subscribe to this mod's changes

gitea-find-issues is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 21d ago), licensed MIT. It adds 124 tokens to every session and 645 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.

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