agentmods.dev

gitea-plan-milestones

gitea-plan-milestones is a skill for Claude Code, Codex from amonstack/gitea_mcp. It costs 108 tokens per session (614 once invoked), scanned A, original, MIT.

A tool for planning work in Gitea, a service for hosting Git repositories and managing software projects, by organizing issues into milestones.

In plain words
What is it for?
Use it to list, inspect, create, edit, or close milestones, including setting descriptions, due dates, and open or closed status.
Why use it?
It keeps project targets and deadlines visible and shows progress without changing the issues themselves.

Skill for Claude CodeCodex

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

not rated 1 changed yesterday A scan 108 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-plan-milestones
Any agent
npx skills add amonstack/gitea_mcp --skill gitea-plan-milestones
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-plan-milestones

README.md
[![agentmods](https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-plan-milestones.svg)](https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-plan-milestones)
Your own site
<a href="https://agentmods.dev/skills/amonstack/gitea_mcp/gitea-plan-milestones"><img src="https://agentmods.dev/badge/skills/amonstack/gitea_mcp/gitea-plan-milestones.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 614 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00108 $0.00614
Opus 5 $0.00054 $0.00307
Sonnet 5 $0.00022 $0.00123
Haiku 4.5 $0.00011 $0.00061

Measured yesterday against content hash c4f22920052f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

gitea-plan-milestones 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.

src/assets/skills/gitea-plan-milestones/SKILL.md · 46 lines

What it actually says

gitea-plan-milestones

When to use

Trigger when the user asks about milestones or release/iteration planning — 中文请求如「建一个 v1.2 里程碑」「看看里程碑进度」「关闭这个迭代」也 MUST 走本 skill。

Create / edit / close milestones. Tools: list_milestones, get_milestone, create_milestone, update_milestone.

Prerequisites

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

list_milestones — DEFAULT-OPEN TRAP

  • Default returns ONLY open milestones. Pass state: "all" or state: "closed" to see the rest, or you will silently miss closed/completed milestones. Paginate 1-based, limit ≤ 100.

create_milestone

  • RULES: title required; description optional; due_on = ISO 8601 (e.g. 2025-12-31T23:59:59Z). Returns the new milestone including its id.

update_milestone

  • RULES: identifies by id (number). PATCH — only title / description / due_on / state you pass change; omit = unchanged. State is open | closed.
  • NOTE: CLOSING a milestone does NOT close its issues — they stay open. Close issues separately (gitea-update-issue) before or after.

get_milestone

  • Read one milestone by id: includes open_issues / closed_issues counts for progress (progress = closed / (open + closed)).

Description template — standardize what you write into description

Milestones succeed when scope is explicit. When creating or editing, structure description with this template; keep it short and drop empty sections.

**Goal:** <the single outcome this milestone delivers>

**Scope**
- In: <what this milestone covers>
- Out: <what is explicitly deferred>

**Acceptance criteria**
- <observable, checkable condition>
- <observable, checkable condition>

**Owners:** <who is accountable>
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. yesterday Changed · +4 lines · +46 tokens per session c4f22920052f
  2. 5d ago First seen · 42 lines · 62 tokens per session scan A a3e2ffe9845b

Subscribe to this mod's changes

gitea-plan-milestones is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 614 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.

Git and workflowProject managementReleases
Related

Other skills, from other repositories

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens