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/harness/harness-ai/template-usagenpx skills add harness/harness-ai --skill template-usagegit 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/template-usage)<a href="https://agentmods.dev/skills/harness/harness-ai/template-usage"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/template-usage.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 | $0.00113 | $0.01232 |
| Opus 5 | $0.00056 | $0.00616 |
| Sonnet 5 | $0.00023 | $0.00246 |
| Haiku 4.5 | $0.00011 | $0.00123 |
Grade A, and why
template-usage 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 4d 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 template-usage — 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Usage Skill
Track template dependencies and usage across Harness via MCP v2 tools.
MCP v2 Tools Used
| Tool | Resource Type | Purpose |
|---|---|---|
harness_search |
template |
Find templates by keyword across orgs/projects |
harness_list |
template |
List templates, filter by scope |
harness_get |
template |
Get template details, versions, and usage references |
harness_describe |
template |
Discover template resource schema and fields |
Templates are managed via harness_list and harness_get only. For creating or updating templates, use the /create-template skill.
Template Types
| Type | Description |
|---|---|
Step |
Single step definition (build, test, deploy actions) |
Stage |
Complete stage with steps (CI stage, CD stage, approval) |
Pipeline |
Full pipeline definition |
StepGroup |
Group of related steps bundled together |
Template Scopes
| Scope | Visibility | Query Parameters |
|---|---|---|
| Account | All orgs and projects | No org_id, no project_id |
| Organization | All projects in the org | org_id only |
| Project | Only within the project | org_id + project_id |
Instructions
Step 1: Find the Template
Search by name or keyword:
harness_search(
query="docker-build-push",
resource_types=["template"],
max_per_type=10,
compact=true
)
Or list templates in a specific scope:
harness_list(
resource_type="template",
org_id="<org>",
project_id="<project>",
search_term="docker"
)
Step 2: Get Template Details
harness_get(
resource_type="template",
resource_id="<template_identifier>",
org_id="<org>",
project_id="<project>"
)
This returns the template definition, version history, and metadata.
Step 3: Check Usage References
harness_get(
resource_type="template",
resource_id="<template_identifier>",
org_id="<org>",
project_id="<project>"
)
Parse the response for referredEntities or usage data. The response includes which pipelines and other templates reference this template.
What ships with it
1 file beside SKILL.md 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.
- 4d ago First seen · 187 lines · 113 tokens per session scan A bb02ae568534
template-usage is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 13d ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,232 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to template-usage, 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…