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-label-issuenpx skills add amonstack/gitea_mcp --skill gitea-label-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-label-issue)<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="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.00082 | $0.00433 |
| Opus 5 | $0.00041 | $0.00217 |
| Sonnet 5 | $0.00016 | $0.00087 |
| Haiku 4.5 | $0.00008 | $0.00043 |
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 3d 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.
What it actually says
gitea-label-issue
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, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_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(paramid). Resolve names→ids vialist_labelswhen 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= issuenumber(URL #N → N).- Adding a non-existent NAME → 404. Confirm names via
list_labelsfirst. - 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; forremove,list_labelsto resolve the id.
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.
- 3d ago First seen · 29 lines · 82 tokens per session scan A d5b3568fe463
gitea-label-issue is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 10d ago), licensed MIT. It adds 82 tokens to every session and 433 once invoked, about $0.0004 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.