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-create-pullnpx skills add amonstack/gitea_mcp --skill gitea-create-pullgit clone --depth 1 https://github.com/amonstack/gitea_mcpWhat 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.00091 | $0.00714 |
| Opus 5 | $0.00046 | $0.00357 |
| Sonnet 5 | $0.00018 | $0.00143 |
| Haiku 4.5 | $0.00009 | $0.00071 |
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 yesterday.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitea-create-pull
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.
## Summary
<1-2 sentences: what this PR changes and why>
## Changes
- <bullet: specific change>
- <bullet: specific change>
## Related issues
Closes #<issue number>
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] Breaking changes noted below
## Breaking changes
<none, or describe>
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.
- yesterday 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 8d ago), licensed MIT. It adds 91 tokens to every session and 714 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.