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 instructions/harness/harness-skills/agents-mdgit 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/instructions/harness/harness-skills/agents-md)<a href="https://agentmods.dev/instructions/harness/harness-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/harness/harness-skills/agents-md.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.02577 | $0.02577 |
| Opus 5 | $0.01288 | $0.01288 |
| Sonnet 5 | $0.00515 | $0.00515 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade A, and why
harness-skills AGENTS.md 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Skills
This repository contains Claude Code skills for working with Harness.io CI/CD platform. All skills use the Harness MCP v2 server's consolidated tool interface.
MCP v2 Server
All skills use the Harness MCP v2 server which provides 10 generic tools operating across 119+ resource types:
| Tool | Purpose |
|---|---|
harness_list |
List resources with filters and pagination |
harness_get |
Get a single resource by ID |
harness_create |
Create a resource (requires confirmation) |
harness_update |
Update a resource (requires confirmation) |
harness_delete |
Delete a resource (requires confirmation) |
harness_execute |
Run, retry, interrupt, sync, toggle, approve, reject, test_connection |
harness_search |
Cross-resource keyword search |
harness_describe |
Local metadata/schema lookup (no API call) |
harness_diagnose |
Pipeline failure analysis |
harness_status |
Project health overview |
Tools accept a resource_type parameter (e.g., pipeline, secret, template) to target specific Harness resources. Tools also support Harness UI URL auto-extraction for org_id, project_id, resource_type, and resource_id.
Skill Directory
Skills live in skills/<skill-name>/SKILL.md. Each skill folder may contain references/, scripts/, and assets/ subdirectories.
Pipeline & Execution
| Skill | Description |
|---|---|
/create-pipeline |
Generate v0 pipeline YAML (CI, CD, combined, approvals) |
/create-pipeline-v1 |
Generate v1 simplified pipeline YAML |
/create-trigger |
Create webhook, scheduled, and artifact triggers |
/create-template |
Create reusable step, stage, pipeline, and step group templates |
/run-pipeline |
Execute and monitor pipeline runs |
/debug-pipeline |
Diagnose pipeline execution failures |
/migrate-pipeline |
Convert v0 pipelines to v1 format |
Infrastructure & Resources
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 · 186 lines · 2,577 tokens per session scan A 55ccb8fcac4f
harness-skills AGENTS.md is an instructions file published in the GitHub repository harness/harness-skills (103 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,577 tokens to every session, about $0.0129 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 instructions, from other repositories
skills AGENTS.md
Instructions for buildkite/skills, covering buildkite skills — agent context, repository structure, skill architecture, skills vs. documentation and key conventions.
AgentStack github-actions-ci-cd-best-practices.instructions.md
Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions. Covers workflow structure, jobs, steps, environment variables, secret management, caching, matrix strategies, testing, and deployment strategies.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.