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-apigit 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-api)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/gitea-api"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/gitea-api.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.00041 | $0.01005 |
| Opus 5 | $0.00020 | $0.00502 |
| Sonnet 5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
gitea-api 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 6d 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.
description: Use when working with the Gitea REST API — authentication, token management, repository/issue/PR CRUD, package management, admin operations, and general API automation with curl. How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitea REST API (v1.26)
Base: https://gitea.example.com/api/v1. Swagger: https://gitea.example.com/api/swagger. OpenAPI spec: https://gitea.example.com/swagger.v1.json.
Authentication
| Method | Header / Param | Use Case |
|---|---|---|
| Token | Authorization: token <token> |
API tokens from Settings > Applications |
| Basic Auth | -u username:password |
Creating tokens (POST /users/:name/tokens) |
| OAuth2 Bearer | Authorization: bearer <token> |
OAuth2 access tokens |
| URL param | ?token=<token> |
Simple scripts |
| SSH signatures | Signature header with SSH key |
mTLS-style auth via SSH |
2FA: add header X-Gitea-OTP: 123456 with Basic Auth.
Token Scopes
"scopes": ["all"] or fine-grained: ["repo", "write:repository", "read:user", "read:organization"]. Create via UI or POST /api/v1/users/{username}/tokens.
Key Endpoints
Users & Auth
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /user |
Current user info |
| GET | /users/{username} |
Get user |
| POST | /users/{username}/tokens |
Create API token (Basic Auth required) |
Repositories
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /repos/{owner}/{repo} |
Get repository |
| POST | /repos/{owner}/{repo} |
Create repository |
| POST | /repos/{owner}/{repo}/mirrors |
Sync mirror |
Issues & Pull Requests
| Method | Endpoint | Purpose |
|---|---|---|
| POST | /repos/{owner}/{repo}/issues |
Create issue |
| GET | /repos/{owner}/{repo}/issues |
List issues (filters: state, labels, created_by) |
| POST | /repos/{owner}/{repo}/pulls |
Create pull request |
| GET | /repos/{owner}/{repo}/pulls |
List PRs |
Organizations
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /orgs/{org} |
Get organization |
| POST | /orgs/{org}/teams |
Create team |
Admin
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /admin/users |
List users (supports sorting/filtering) |
| POST | /admin/users |
Create user |
| POST | /admin/hooks |
Create system/default webhook |
| GET | /admin/hooks?type=system|default |
List admin webhooks |
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.
- 6d ago First seen · 105 lines · 41 tokens per session scan A efb4e0abbcc8
gitea-api is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 1,005 once invoked, about $0.0002 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
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-changelog
Manages changelog entries for Prowler components following keepachangelog.com format. Trigger: When creating PRs, adding changelog entries, or working with any CHANGELOG.md file in ui/, api/, mcpserver/, or prowler/.
writing-emdash-docs
Write, revise, and review EmDash documentation for technical accuracy, useful structure, house style, and natural prose. Use when working on user documentation, guides, API reference pages, migration or upgrade guides, READMEs, contributor documentation, technical specifications, or release notes in the EmDash…
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
managing-endpoint-versions
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without…