agentmods.dev

gitea-find-issues

gitea-find-issues is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 90 tokens per session (558 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

not rated 1 10d ago A scan 90 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-find-issues
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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00090 $0.00558
Opus 5 $0.00045 $0.00279
Sonnet 5 $0.00018 $0.00112
Haiku 4.5 $0.00009 $0.00056

Measured 3d ago against content hash 4978812b33ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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 · 32 lines

What it actually says

gitea-find-issues

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. 3d 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 10d ago), licensed MIT. It adds 90 tokens to every session and 558 once invoked, about $0.0005 per session on Opus 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 workflow
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens