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/deevus/tea-skills/close-issuesnpx skills add deevus/tea-skills --skill close-issuesgit clone --depth 1 https://github.com/deevus/tea-skillsWrote 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/deevus/tea-skills/close-issues)<a href="https://agentmods.dev/skills/deevus/tea-skills/close-issues"><img src="https://agentmods.dev/badge/skills/deevus/tea-skills/close-issues.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.00025 | $0.00128 |
| Opus 5 | $0.00013 | $0.00064 |
| Sonnet 5 | $0.00005 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
close-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.
What it actually says
Close / Reopen Issues
Close
tea issues close 42
tea issues close 1 2 3 # close multiple
Reopen
tea issues reopen 42
Bulk Close by Label
tea issues list --labels "wontfix" --output json | jq -r '.[].index' | xargs tea issues close
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 · 27 lines · 25 tokens per session scan A c3e965e6e60d
close-issues is a skill published in the GitHub repository deevus/tea-skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 128 once invoked, about $0.0001 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
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.
today-drink-tea
根据当前日期、时间、季节，从用户家茶叶库存中推荐"今天喝什么"，输出400ml壶泡法（只泡一泡、茶水分离、TDS20纯净水）的投茶量、水温、浸泡时间。当用户问"今天喝什么""推荐一款茶""喝哪款"时触发；问"今天冷泡什么""冷泡推荐"时输出1.6L冷泡壶方案（投茶量、冷藏时长、可饮时间）；用户说"XX太淡/太苦/涩"等喝感反馈时复盘调参，说"XX仓气重/仓味/堆味/霉味"或"洗茶太过/香味洗掉"时调整洗茶档位，说"XX闷味/闷熟"或"XX香气散/跑香"时调整盖盖/开盖，说"XX泡酸/发酸"或"XX香味没了/没香气"时降低水温（见"复盘调校"节）；说"我搬到了外地"时清空全部库存（随后"我买了XX、YY、ZZ"批量导入自己的茶单）；说…
git-forge-migration
Migrate repos between git forges (GitHub/Gitea/Codeberg).
git-flow
Větvení, checkpointy a odevzdání práce přes agenticdev-git.
kontext
Načte kontext klienta z prd/ — glosář, požadavky, rozhodnutí.
code-review
Use to review a fixed diff against its specification and repository standards.