agentmods.dev

gitea-find-pulls

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

A read-only tool for finding and inspecting pull requests in Gitea repositories. Gitea is a self-hosted service for Git repositories and code review.

In plain words
What is it for?
Listing or searching pull requests, reading one pull request's details, and reviewing its commits or changed files without modifying it.
Why use it?
It prevents confusion when locating pull requests across repositories and provides rules for selecting the right repository, filters, and pagination.

Skill for Claude CodeCodex

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

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

Good fit Listing or searching pull requests, reading one pull request's details, and reviewing its commits or changed files without modifying it.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-find-pulls"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-find-pulls.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 849 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.00139 $0.00849
Opus 5.5 $0.00056 $0.00340
Sonnet 5.5 $0.00028 $0.00170
Haiku 4.5 $0.00014 $0.00085

Measured 1mo ago against content hash 8fa68bd66ecb, 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-pulls 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-pulls/SKILL.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gitea-find-pulls

When to use

Trigger when the user asks to list / search / read pull requests — 中文请求如「看看开放的 PR」「这个 PR 改了哪些文件」「搜一下相关的合并请求」也 MUST 走本 skill。

Read-only pull request discovery. Tools: list_pull_requests, search_issues, get_pull_request, list_pull_commits, list_pull_files.

Prerequisites

  • Resolve owner+repo for list_pull_requests/get_pull_request/list_pull_commits/list_pull_files: 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 PRs, filtered by state/labels/sort/milestone → list_pull_requests.
  • ACROSS repos by keyword → search_issues({ type: "pulls" }) (global; no owner/repo).
  • ONE PR's full detail (branches, mergeable, merged) → get_pull_request.
  • Commits in one PR → list_pull_commits.
  • Files changed in one PR → list_pull_files.

list_pull_requests

  • RULES: labels = comma-separated NAMES, AND-matched; a mistyped or non-existent name returns EMPTY with no error. sort options: oldest, recentupdate, leastupdate, mostcomment, leastcomment, priority. state default is open.
  • CHECK FIRST: confirm label names via list_labels (gitea-manage-labels) before filtering by labels.
  • 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. Set type: "pulls" to search only PRs. labels = names. query matches title + body.
  • CHECK FIRST: set type deliberately.
  • CHECK AFTER: page fully if completeness matters.

get_pull_request

  • RULES: pass index = the PR number (URL #42 → 42), never the internal id.
  • NOTE: the response carries mergeable (boolean), merged (boolean), merged_at, draft, plus base/head branch objects. Check mergeable before attempting a merge (gitea-merge-pull).

Read the full file on GitHub · 44 lines

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 · +45 tokens per session 8fa68bd66ecb
  2. 1mo ago First seen · 40 lines · 94 tokens per session scan A ecc225d3d343

Subscribe to this mod's changes

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

Code reviewGit and workflow
Related

Other skills, from other repositories

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens