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 harness/harness-skills --skill manage-artifactsgit clone --depth 1 https://github.com/harness/harness-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/harness/harness-skills/manage-artifacts)<a href="https://agentmods.dev/skills/harness/harness-skills/manage-artifacts"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-artifacts/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/harness/harness-skills/manage-artifacts"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-artifacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00140 | $0.01150 |
| Opus 5 | $0.00070 | $0.00575 |
| Sonnet 5 | $0.00028 | $0.00230 |
| Haiku 4.5 | $0.00014 | $0.00115 |
Grade A, and why
manage-artifacts 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- manage-artifacts — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Artifacts
Configure private artifact registries, security scanning policies, and cross-region replication in Harness Artifact Registry.
Instructions
Step 1: Establish Scope
Confirm the user's org, project, and artifact format requirements.
Call MCP tool: harness_list
Parameters:
resource_type: "project"
org_id: "<organization>"
Step 2: Identify the AR Task
Determine which workflow the user needs:
- Private Registry Setup -- Docker, Helm, Maven, npm, PyPI repositories with RBAC
- Security Scanning Policy -- Vulnerability scanning with CVE thresholds and license checks
Step 3: Configure Private Registry
Gather from the user:
- Artifact formats to support (Docker, Helm, Maven, npm, PyPI)
- Upstream proxy preferences (Docker Hub, ECR Public, GCR)
- Image signing requirements (Cosign, Notary, none)
- Multi-architecture support needs
Docker Registry:
- Repository name and upstream proxy configuration
- Image signing with Cosign or Notary v2
- Multi-arch support (amd64 + arm64)
Helm Chart Repository:
- Chart validation on push
- Dependency resolution enabled
Additional Formats (Maven, npm, PyPI):
- Separate repositories per format
- Snapshot/release policies
- Upstream proxies for public registries
Access Controls:
- Read access: all developers in the org scope
- Push access: CI/CD service accounts only (no personal credentials)
- Admin: platform team
- LDAP/SAML integration with identity provider
Replication:
- Primary region with replication to secondary regions
- Configurable sync interval (real-time, 15 minutes, hourly, daily)
Step 4: Configure Security Scanning Policies
Gather from the user:
- Artifact types to scan
- Security scanner (Aqua Trivy, Snyk, Grype, Prisma Cloud)
- CVE severity thresholds (block on CRITICAL and HIGH above N)
Configure scanning policies:
- Scan on push and periodic rescans for stored artifacts
- Block download if critical or high CVE count exceeds thresholds
- License compliance: block artifacts with disallowed licenses (GPL-3.0, AGPL)
- SBOM generation: auto-generate CycloneDX or SPDX on every scan
- Exemption workflow: security team can approve specific CVEs with expiry dates
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.
- 10d ago First seen · 144 lines · 140 tokens per session scan A 47f41484ef6b
manage-artifacts is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 140 tokens to every session and 1,150 once invoked, about $0.0007 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-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
personal-shopper
Personal advisor for a problem that might be solved by buying something — diagnoses the real need through conversation, then recommends products from the user's configured stores only when a purchase is the right answer. Recalls the user's sizes, budget, brands and restrictions across sessions, and records new ones as…
azure-prepare
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
azure-kubernetes-app-deploy
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…