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 Aidas-dev/k8s-agent-skills --skill gitea-teagit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-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/aidas-dev/k8s-agent-skills/gitea-tea)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/gitea-tea"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/gitea-tea/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/gitea-tea"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/gitea-tea.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01838 |
| Opus 5 | $0.00028 | $0.00919 |
| Sonnet 5 | $0.00011 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
gitea-tea scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Runner container needs tools that workflows require (curl, git, etc.) How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitea + tea CLI
Use this skill when tasks target Gitea and the tea CLI, especially if the user would normally use gh on GitHub.
When To Use
- User mentions Gitea, self-hosted git, forgejo-compatible flows, or
tea - You need CLI automation for issues, pull requests, repos, comments, or releases
- You need host-specific auth profiles (multiple Gitea instances)
- Managing Gitea Actions (secrets, variables, runners, workflow runs)
- Managing webhooks, notifications, or admin tasks
Core Rules
- Prefer
teaoverghfor Gitea targets. - Always scope commands to target explicitly when ambiguity exists:
--repo owner/name--login <profile>--remote <remote-name>
- If command flags differ by tea version, run
tea <cmd> --helpfirst and follow local help text. - For PR/review actions, ensure local branches are pushed before create/merge operations.
Auth Workflow
Create login profile (token)
tea logins add --name <profile> --url https://git.example.com --token <token>
Verify logins / switch default
tea logins ls
tea logins default <profile>
Quick auth check
tea whoami # Show current user
Optional env-based auth (automation)
GITEA_SERVER_URLGITEA_SERVER_TOKENGITEA_SERVER_USERGITEA_SERVER_PASSWORD
Command Mapping (gh -> tea)
- Repo list:
gh repo list->tea repos ls - Issue list:
gh issue list->tea issues ls - Issue create:
gh issue create->tea issues create - PR list:
gh pr list->tea pulls lsortea pr ls - PR create:
gh pr create->tea pulls create - PR checkout:
gh pr checkout <n>->tea pulls checkout <n> - Comment on PR/issue:
gh pr comment/gh issue comment->tea comment <index> [body] - Release list/create:
gh release list/create->tea releases ls/tea releases create
Practical Patterns
Work on a specific repo
tea issues ls --repo owner/name --login <profile>
tea pulls ls --repo owner/name --login <profile>
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.
- 9d ago First seen · 215 lines · 55 tokens per session scan A 6964bc2e5e02
gitea-tea is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 55 tokens to every session and 1,838 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.