A set of commands for listing and inspecting issues in Gitea or Forgejo, platforms for hosting Git repositories. It supports filters such as labels, milestones, people, dates, and search terms.

Viewing repository issues, filtering them by status or metadata, reading issue details and comments, exporting results, and counting matches.

Large issue lists are difficult to review without filtering, pagination, or machine-readable output. These commands help find the relevant work and inspect individual issues.

list-issues — Skill for Claude Code and Codex by deevus: A set of commands for listing and inspecting issues…

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/deevus/tea-skills/list-issues

Any agent

npx skills add deevus/tea-skills --skill list-issues

Clone the repo

git clone --depth 1 https://github.com/deevus/tea-skills

Made for: Claude Code, Codex.

Or install tea, the plugin that ships this one along with the rest of its 16 skills, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/deevus/tea-skills/list-issues.svg)](https://agentmods.dev/skills/deevus/tea-skills/list-issues)

Your own site

<a href="https://agentmods.dev/skills/deevus/tea-skills/list-issues"><img src="https://agentmods.dev/badge/skills/deevus/tea-skills/list-issues.svg" alt="Measured on agentmods" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 557 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.

Model	Per session	Once invoked
Fable 5	$0.00031	$0.00557
Opus 5	$0.00015	$0.00279
Sonnet 5	$0.00006	$0.00111
Haiku 4.5	$0.00003	$0.00056

Measured 5d ago against content hash da6d6ad30be3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

list-issues 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 5d 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.

skills/list-issues/SKILL.md · 52 lines

What it actually says

List Issues

List

# Repository-scoped listing: prefer an explicit remote or repo/login.
tea issues list --remote <git-remote> -o simple           # e.g. --remote self-hosted
tea issues list --repo <owner>/<repo> --login <login> -o simple

# Add filters to the same repository-scoped command.
tea issues list --remote <git-remote> --state all -o simple              # include closed
tea issues list --remote <git-remote> --labels "bug,critical" -o simple  # by label
tea issues list --remote <git-remote> --milestones "v1.0" -o simple      # by milestone
tea issues list --remote <git-remote> --assignee "user" --author "user"  # by person
tea issues list --remote <git-remote> --keyword "search term"            # text search
tea issues list --remote <git-remote> --from "2025-01-01" --until "2025-06-01"
tea issues list --remote <git-remote> --output json                      # use json only when parsing with jq
tea issues list --remote <git-remote> --fields "index,title,state,labels,assignees"
tea issues list --remote <git-remote> --page 2 --limit 50

Show

tea issues --remote <git-remote> 42              # detail view
tea issues --remote <git-remote> 42 --comments   # with comments

Export / Count

# Export all issues in this repository to JSON
tea issues list --remote <git-remote> --state all --output json > issues-backup.json

# Count by state in this repository
echo "Open: $(tea issues list --remote <git-remote> --state open --output json | jq length)"
echo "Closed: $(tea issues list --remote <git-remote> --state closed --output json | jq length)"

Tips

Do not use bare tea issues list when the user asks for issues for the current repository; in multi-repo logins it can return issues across repositories.
Prefer -o simple for listing; use --output json only when parsing with jq
--kind pulls searches PRs with the same filters as issues

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.

5d ago First seen · 52 lines · 31 tokens per session scan A da6d6ad30be3

Subscribe to this mod's changes

list-issues is a skill published in the GitHub repository deevus/tea-skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 557 once invoked, about $0.0002 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 workflow agent-skills claude-code cli forgejo gitea tea

docs

This is the project knowledge base. It covers the conventions, workflows, and principles you need to work on gitea-mcp-server. Everything here is available directly — no skill loading required.

pxsloot/gitea-mcp-server · 0 tokens

today-drink-tea

根据当前日期、时间、季节，从用户家茶叶库存中推荐"今天喝什么"，输出400ml壶泡法（只泡一泡、茶水分离、TDS20纯净水）的投茶量、水温、浸泡时间。当用户问"今天喝什么""推荐一款茶""喝哪款"时触发；问"今天冷泡什么""冷泡推荐"时输出1.6L冷泡壶方案（投茶量、冷藏时长、可饮时间）；用户说"XX太淡/太苦/涩"等喝感反馈时复盘调参，说"XX仓气重/仓味/堆味/霉味"或"洗茶太过/香味洗掉"时调整洗茶档位，说"XX闷味/闷熟"或"XX香气散/跑香"时调整盖盖/开盖，说"XX泡酸/发酸"或"XX香味没了/没香气"时降低水温（见"复盘调校"节）；说"我搬到了外地"时清空全部库存（随后"我买了XX、YY、ZZ"批量导入自己的茶单）；说…

blyatman996/Tea-Chay-Advisor · 321 tokens

list-issues