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-update-issuenpx skills add amonstack/gitea_mcp --skill gitea-update-issuegit 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-update-issue)<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-update-issue"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-update-issue.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.00113 | $0.00489 |
| Opus 5 | $0.00056 | $0.00244 |
| Sonnet 5 | $0.00023 | $0.00098 |
| Haiku 4.5 | $0.00011 | $0.00049 |
Grade A, and why
gitea-update-issue 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-update-issue
When to use
Trigger when the user asks to edit / close / reopen an issue, or set its assignee/milestone — 中文请求如「关掉这个 issue」「重新打开」「把它指派给某人」「挂到 v1.2 里程碑」也 MUST 走本 skill。
Edit one issue's fields or change its state. Tools: get_issue, update_issue.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo). - There is NO optimistic locking — always read current state first.
Flow
- READ CURRENT:
get_issue({ index })—index= issuenumber(URL #N → N), never the internalid. - APPLY:
update_issue({ index, ...changedFields }).
update_issue
- RULES: PATCH — only fields you pass change; omit = unchanged. To CLEAR a field pass its EMPTY form, do NOT omit it:
milestone: 0clears the milestone,assignees: []clears assignees. Useassignees(array), not the deprecatedassignee. State values areopen|closed. - NOT FOR single-label changes:
labelshere are IDs and REPLACE the entire set — to add/remove one label useadd_issue_labels/remove_issue_label(gitea-label-issue). - CHECK FIRST:
get_issuefor current values if state may have changed since your last read; state the intended change to the user before writing.
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 · +37 tokens per session 3b4191585e1a
- 3d ago First seen · 22 lines · 76 tokens per session scan A c3a44253fcbe
gitea-update-issue is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 489 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…