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.
npx skills add amonstack/gitea_mcp --skill gitea-create-pullgit clone --depth 1 https://github.com/amonstack/gitea_mcpWrote 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.
[](https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-create-pull)<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-create-pull"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-create-pull/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.
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-create-pull"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-create-pull.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00125 | $0.00815 |
| Opus 5.5 | $0.00050 | $0.00326 |
| Sonnet 5.5 | $0.00025 | $0.00163 |
| Haiku 4.5 | $0.00013 | $0.00081 |
Grade A, and why
gitea-create-pull 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitea-create-pull
When to use
Trigger when the user asks to create / open a pull request — 中文请求如「提个 PR」「发起合并请求」「把这个分支做成 PR」也 MUST 走本 skill:先确认分支存在且无同 head/base 的开放 PR,再创建。
Open one new pull request after ruling out a duplicate. Tools: list_pull_requests, create_pull_request.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo). Never guess — wrong values create the PR in the wrong repo. - The
head(source) branch MUST already exist and contain the commits to merge; thebase(target) branch is typically the default branch.
Flow
- DUPLICATE CHECK (always first):
list_pull_requests({ state: "open" }). If an open PR with the samehead/basealready exists, comment on it (gitea-comment-issue) instead of creating a duplicate. Do NOT skip this — creation does not de-duplicate. - CREATE:
create_pull_request({ title, head, base, body? }).
create_pull_request
- RULES:
title,head, andbaseare required. For cross-fork PRs use"owner:branch"inhead(e.g."ake131998:feat/my-change").bodyis Markdown. - Do NOT pass
labelsormilestonehere:labelsexpect IDs (error-prone). Create WITHOUT them, then attach labels by name viaadd_issue_labels(gitea-label-issue — PR #N == Issue #N) and set the milestone viaupdate_pull_request. - WIP / draft: Gitea blocks merges when the title starts with
WIP:,[WIP], orDraft:. Prefix the title while work is in progress; remove the prefix when ready to merge (gitea-update-pull). - CHECK FIRST: confirm no duplicate open PR (step 1), that
headexists and is pushed, and thatowner/repoare correct before writing. - CHECK AFTER: the returned object's
numberis the new PR index;mergeableindicates whether Gitea can auto-merge it.
Body template — standardize what you write into body
Always structure body. Ask the user for details if the change is not obvious. Drop a section only when it is genuinely empty; never invent data.
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.
- 1mo ago Changed · +4 lines · +34 tokens per session 3fe6484c7df8
- 1mo ago First seen · 49 lines · 91 tokens per session scan A 31989e08b426
gitea-create-pull is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 21d ago), licensed MIT. It adds 125 tokens to every session and 815 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.
Other skills, from other repositories
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.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.