agentmods.dev

gitea-label-issue

gitea-label-issue is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 119 tokens per session (527 once invoked), scanned A, original, MIT.

A tool for managing the labels attached to one Gitea issue. Labels are tags used to classify and filter project tasks.

In plain words
What is it for?
Use it to add, replace, remove, or clear labels on an issue, and to list available labels before making changes.
Why use it?
It avoids common mistakes such as using a label's name where Gitea requires its numeric ID.

Skill for Claude CodeCodex

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

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

Good fit Use it to add, replace, remove, or clear labels on an issue, and to list available labels before making changes.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-label-issue"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-label-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 527 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.00119 $0.00527
Opus 5.5 $0.00048 $0.00211
Sonnet 5.5 $0.00024 $0.00105
Haiku 4.5 $0.00012 $0.00053

Measured 1mo ago against content hash ca487783467e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitea-label-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 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-label-issue/SKILL.md · 33 lines

What it actually says

gitea-label-issue

When to use

Trigger when the user asks to label / tag / relabel / unlabel an issue or PR — 中文请求如「给这个 issue 打个 bug 标签」「把标签清掉」「换成 enhancement」也 MUST 走本 skill。

Manage the labels ON one issue. Tools: list_labels, add_issue_labels, replace_issue_labels, remove_issue_label, clear_issue_labels.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo).

CRITICAL — name vs id (the endpoints are inconsistent)

  • BY NAME (string[]): add_issue_labels, replace_issue_labels.
  • BY ID (number): remove_issue_label (param id). Resolve names→ids via list_labels when you need an id.

Choose the tool

  • ADD labels (keep existing) → add_issue_labels({ index, labels: [names] }).
  • SET the exact label set (overwrites all) → replace_issue_labels({ index, labels: [names] }).
  • REMOVE ONE label → remove_issue_label({ index, id }) (id, not name).
  • REMOVE ALL → clear_issue_labels({ index }).

Rules

  • index = issue number (URL #N → N).
  • Adding a non-existent NAME → 404. Confirm names via list_labels first.
  • Scoped/exclusive labels (scope/name) are mutually exclusive within a scope — adding one may replace another in the same scope.
  • CHECK FIRST: for replace, get_issue (gitea-find-issues) to see current labels so you don't drop one unintentionally; for remove, list_labels to resolve the id.
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 · +37 tokens per session ca487783467e
  2. 1mo ago First seen · 29 lines · 82 tokens per session scan A d5b3568fe463

Subscribe to this mod's changes

gitea-label-issue is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 21d ago), licensed MIT. It adds 119 tokens to every session and 527 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.

Project management
Related

Other skills, from other repositories

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens