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 skills add amonstack/gitea_mcp --skill gitea-manage-labelsgit 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-manage-labels)<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-manage-labels"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-manage-labels.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.1 | $0.00099 | $0.00419 |
| Opus 5 | $0.00049 | $0.00210 |
| Sonnet 5 | $0.00020 | $0.00084 |
| Haiku 4.5 | $0.00010 | $0.00042 |
Grade A, and why
gitea-manage-labels 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-manage-labels
When to use
Trigger when the user asks to create or edit a label definition — 中文请求如「新建一个标签」「把这个标签的颜色/描述改掉」也 MUST 走本 skill。
Create or edit the repo's label definitions. Tools: list_labels, create_label, update_label.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo).
list_labels
- Enumerate available labels (name, id, color, description). Use to resolve names→ids and to check name uniqueness before create. Paginate 1-based,
limit≤ 100.
create_label
- RULES:
namerequired and UNIQUE per repo (duplicate → conflict).color= 6-digit hex, with or without leading#(e.g.#ff0000orff0000).descriptionoptional. - CHECK FIRST:
list_labelsto avoid a name collision.
update_label
- RULES: identifies the label by
id(number). PATCH — onlyname/color/descriptionyou pass change; omit = unchanged.colorstays 6-digit hex. - NOTE: renaming or recoloring a label updates it on EVERY issue that currently has it.
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 Changed · +4 lines · +39 tokens per session 937dc5aa3e0d
- 7d ago First seen · 23 lines · 60 tokens per session scan A 459dbb84a027
gitea-manage-labels is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 99 tokens to every session and 419 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.