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-ai --skill manage-delegatesgit clone --depth 1 https://github.com/harness/harness-aiWrote 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-ai/manage-delegates)<a href="https://agentmods.dev/skills/harness/harness-ai/manage-delegates"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/manage-delegates.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.00087 | $0.00998 |
| Opus 5 | $0.00044 | $0.00499 |
| Sonnet 5 | $0.00017 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
manage-delegates 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 8d 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.
This is a copy
100% identical to manage-delegates — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Delegates
Monitor delegate health and manage registration tokens via MCP.
Instructions
Step 1: List Delegates
List all delegates in the account to check health and connectivity:
Call MCP tool: harness_list
Parameters:
resource_type: "delegate"
This returns all delegates with their status, version, connectivity, and last heartbeat. Delegates are account-scoped -- no org/project needed.
Step 2: List Delegate Tokens
Call MCP tool: harness_list
Parameters:
resource_type: "delegate_token"
org_id: "<organization>"
project_id: "<project>"
Filter by name or status:
Call MCP tool: harness_list
Parameters:
resource_type: "delegate_token"
name: "prod-token"
status: "ACTIVE"
Step 3: Get Token Details
Call MCP tool: harness_get
Parameters:
resource_type: "delegate_token"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 4: Create a Token
Call MCP tool: harness_create
Parameters:
resource_type: "delegate_token"
org_id: "<organization>"
project_id: "<project>"
body:
name: "prod-delegate-token"
Step 5: Find Delegates for a Token
Call MCP tool: harness_execute
Parameters:
resource_type: "delegate_token"
action: "get_delegates"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 6: Revoke a Token
Call MCP tool: harness_execute
Parameters:
resource_type: "delegate_token"
action: "revoke"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Step 7: Delete a Token
Call MCP tool: harness_delete
Parameters:
resource_type: "delegate_token"
resource_id: "<token_name>"
org_id: "<organization>"
project_id: "<project>"
Resource Types
| Resource Type | Scope | Operations | Description |
|---|---|---|---|
delegate |
Account | list | List delegates with health status |
delegate_token |
Project | list, get, create, delete + revoke, get_delegates actions | Manage registration tokens |
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.
- 8d ago First seen · 149 lines · 87 tokens per session scan A b13c9fac9ba8
manage-delegates is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 17d ago), licensed Apache-2.0. It adds 87 tokens to every session and 998 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to manage-delegates, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…