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.
git 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/plugins/harness/harness-skills/harness-infrastructure)<a href="https://agentmods.dev/plugins/harness/harness-skills/harness-infrastructure"><img src="https://agentmods.dev/badge/plugins/harness/harness-skills/harness-infrastructure/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/plugins/harness/harness-skills/harness-infrastructure"><img src="https://agentmods.dev/badge/plugins/harness/harness-skills/harness-infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
harness-infrastructure 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 yesterday.
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
{
"name": "harness-infrastructure",
"displayName": "Harness Infrastructure & Resources",
"description": "5 skills: Define services, environments, infrastructure, connectors and secrets for Harness deployments.",
"source": ".",
"strict": false,
"skills": [
"./skills/infrastructure"
],
"category": "infrastructure",
"keywords": [
"harness",
"services",
"environments",
"connectors",
"secrets"
],
"author": {
"name": "Harness"
},
"repository": "https://github.com/harness/harness-skills",
"license": "Apache-2.0"
}What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 417 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#harness-infrastructure in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 23 lines scan A 0360fb602113
harness-infrastructure is a plugin published in the GitHub repository harness/harness-skills (117 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-15.
Other plugins, from other repositories
azure-local-skills
Azure Local skills covering standard deployments (Azure Stack HCI, 1-16 node hyperconverged, rack-aware clusters) and multi-rack (rack scale) deployments built on Network Fabric Controller, Cluster Manager, and managed network fabric.
azure-advisor
Azure Advisor recommendations, service-retirement impact, and customer-ready remediation guidance.
azure-sdk-rust
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.
railway
Railway agent skills and hosted MCP server for deploying, configuring, monitoring, and troubleshooting apps and infrastructure on Railway from Claude Code. Manage services, environments, deployments, databases, object storage, networking, and observability.
fleet
Agent-to-agent reach across a personal fleet (fleet:reach): from any Claude Code lane (WSL or native Windows, any machine), run a script, prompt, or query and wait, message a session, or start a named session in another lane. Each lane signs into its own Claude account, so built-in peer tools see only their own lane.…
agent-fs
Agent-first filesystem CLI — store, search, and version files backed by S3.