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 agentmods add skills/amonstack/gitea_mcp/gitea-merge-pullnpx skills add amonstack/gitea_mcp --skill gitea-merge-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-merge-pull)<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-merge-pull"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-merge-pull.svg" alt="Measured on agentmods" 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 | $0.00126 | $0.00687 |
| Opus 5 | $0.00063 | $0.00344 |
| Sonnet 5 | $0.00025 | $0.00137 |
| Haiku 4.5 | $0.00013 | $0.00069 |
Grade A, and why
gitea-merge-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 today.
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.
What it actually says
gitea-merge-pull
When to use
Trigger when the user asks to merge a pull request — 中文请求如「把这个 PR 合了」「合并到 master」「squash 合入」也 MUST 走本 skill：IRREVERSIBLE，先确认 mergeable 并取得用户对策略的明确批准。
Merge one pull request. IRREVERSIBLE. Tools: get_pull_request, is_pull_merged, merge_pull_request.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo). - This is DESTRUCTIVE and IRREVERSIBLE — merging is final. Always confirm the index, the strategy, and the user's approval BEFORE calling
merge_pull_request.
Flow
- CHECK MERGED:
is_pull_merged({ index })— if already merged, STOP and report; do not attempt a redundant merge. - CHECK MERGEABLE:
get_pull_request({ index })— confirmmergeable: true,state: "open", and that the PR is notdraftor WIP-titled. Ifmergeableis false or null, STOP — conflicts must be resolved on the branch first. - CONFIRM: state the index, the chosen
Dostrategy, and ask the user for explicit approval. - MERGE:
merge_pull_request({ index, Do, MergeTitleField?, MergeMessageField?, SHA? }).
merge_pull_request
- RULES:
Dois required and selects the strategy:merge— creates a merge commit (preserves all individual commits).squash— squashes all commits into one on the base branch.rebase— rebases commits onto the base branch, then fast-forwards.rebase-merge— rebases commits, then creates a merge commit.
MergeTitleField/MergeMessageFieldcustomize the merge commit message.SHApins the expected HEAD — the merge FAILS if the branch moved since (guards against racing pushes).- CHECK FIRST:
is_pull_merged(step 1) +get_pull_requestmergeable(step 2) + user confirmation (step 3). - CHECK AFTER: the tool returns a text confirmation. If it errors with 409, the PR is not mergeable (conflicts or already merged) — re-read
get_pull_requestand do NOT retry blindly.
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.
- today Changed · +4 lines · +36 tokens per session 7117b9fa98ee
- 4d ago First seen · 29 lines · 90 tokens per session scan A 91732731999e
gitea-merge-pull is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 687 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…