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/aidas-dev/k8s-agent-skills/harbor-apinpx skills add Aidas-dev/k8s-agent-skills --skill harbor-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/harbor-api)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/harbor-api"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/harbor-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.00045 | $0.02572 |
| Opus 5 | $0.00023 | $0.01286 |
| Sonnet 5 | $0.00009 | $0.00514 |
| Haiku 4.5 | $0.00005 | $0.00257 |
Grade A, and why
harbor-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 Harbor REST API v2 — project management, artifact operations, robot accounts, replication, vulnerability scanning, OIDC/LDAP config, garbage collection, and general API automation w How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harbor REST API v2
Base: /api/v2.0. Latest stable: Harbor v2.15.1 (May 2026). API spec: Swagger 2.0 at api/v2.0/swagger.yaml. Built-in Swagger UI: https://<harbor>/devcenter-api-2.0.
Authentication
| Method | Header / Usage | Use Case |
|---|---|---|
| Basic Auth | -u username:password |
Direct admin/developer API access |
| Bearer Token | Authorization: Bearer <token> |
Obtained from /service/token per Docker Registry v2 spec |
| Robot Account | -u robot$<prefix><name>:<secret> |
Automated CI/CD with scoped permissions |
| OIDC ID Token | Authorization: Bearer <oidc_id_token> |
OIDC-authenticated users (basic auth not supported for OIDC) |
Bearer Token Flow
# Get token for push/pull access to a repo
TOKEN=$(curl -s -u "username:password" \
"https://harbor.example.com/service/token?service=harbor-registry&scope=repository:project/repo:pull,push" \
| jq -r '.token')
# Use for registry operations
curl -H "Authorization: Bearer $TOKEN" https://harbor.example.com/v2/_catalog
Robot Account Notes
- Secret shown only once at creation — Harbor does not store it
- Username format:
robot$<prefix><account_name> - System-level (v2.2.0+) or project-level scope
- Permissions: granular RBAC (push, pull, create, read, delete, list, etc.)
Key Endpoints
Health & Status
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /health |
Component health (no auth) |
| GET | /statistics |
Project & repo statistics |
| GET | /search?q=<query> |
Search projects, repos, helm charts |
Project Management
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /projects |
List projects (filter: name, public, owner) |
| POST | /projects |
Create project |
| HEAD | /projects |
Check project name exists |
| GET | /projects/{name_or_id} |
Get project |
| PUT | /projects/{name_or_id} |
Update project |
| DELETE | /projects/{name_or_id} |
Delete project |
| GET | /projects/{name_or_id}/_deletable |
Check if deletable |
| GET | /projects/{name_or_id}/summary |
Project summary |
| GET | /projects/{name_or_id}/metadatas |
List metadata |
| POST | /projects/{name_or_id}/metadatas |
Add metadata |
| GET/PUT/DELETE | /projects/{name_or_id}/metadatas/{meta_name} |
CRUD metadata entry |
| GET | /projects/{name_or_id}/members |
List members |
| POST | /projects/{name_or_id}/members |
Add member |
| GET/PUT/DELETE | /projects/{name_or_id}/members/{mid} |
CRUD member |
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 · 232 lines · 45 tokens per session scan A 2efb7e59ba47
harbor-api is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 23d ago), licensed MIT. It adds 45 tokens to every session and 2,572 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
apify-actor-development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
enterprise
Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. For multi-feature initiatives spanning a release timeline, combine with /sprint master-plan (v2.1.13) to group features into a single 8-phase sprint container with shared scope/budget and 4 auto-pause triggers…
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
chatwoot
Self-host customer support with Chatwoot. Use when a user asks to set up open-source customer support, add live chat without SaaS costs, build a multi-channel inbox, or deploy a free Intercom alternative.
gcp-essentials
Use when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege IAM wiring them together. NOT AWS (that is aws-essentials), NOT the CI pipeline that ships the image (that is deployment), NOT Postgres…