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 debug-pipelinegit 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/debug-pipeline)<a href="https://agentmods.dev/skills/harness/harness-skills/debug-pipeline"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/debug-pipeline/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/debug-pipeline"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/debug-pipeline.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.00121 | $0.01500 |
| Opus 5 | $0.00060 | $0.00750 |
| Sonnet 5 | $0.00024 | $0.00300 |
| Haiku 4.5 | $0.00012 | $0.00150 |
Grade A, and why
debug-pipeline 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 9d 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:
- debug-pipeline — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Pipeline
Diagnose pipeline executions and suggest fixes via MCP.
Instructions
Step 1: Diagnose Execution (Preferred)
Use the dedicated diagnosis tool. It accepts an execution_id, pipeline_id (auto-fetches latest execution), or a Harness URL:
Call MCP tool: harness_diagnose
Parameters:
pipeline_id: "<pipeline_identifier>" # or execution_id or url
org_id: "<organization>"
project_id: "<project>"
This returns a structured report with stage/step breakdown, timing, bottlenecks, and failure details in one call. It also automatically follows chained (child) pipeline failures.
Step 1b: Full Diagnostic Mode
For deeper analysis, request logs and pipeline YAML:
Call MCP tool: harness_diagnose
Parameters:
execution_id: "<execution_id>"
org_id: "<organization>"
project_id: "<project>"
summary: false # raw diagnostic payload
include_yaml: true # include pipeline definition
include_logs: true # include failed step logs
log_snippet_lines: 120 # tail N lines per step (0 = unlimited)
max_failed_steps: 5 # cap number of steps to fetch logs for
Diagnose Parameters
| Parameter | Default | Description |
|---|---|---|
execution_id |
-- | Specific execution to analyze |
pipeline_id |
-- | Fetch latest execution for this pipeline |
url |
-- | Harness UI URL (auto-extracts IDs) |
summary |
true | Structured report (true) or raw payload (false) |
include_yaml |
false (summary) / true (raw) | Include pipeline YAML definition |
include_logs |
false (summary) / true (raw) | Include failed step logs |
log_snippet_lines |
120 | Max log lines per step (tail). 0 = unlimited |
max_failed_steps |
5 | Max steps to fetch logs for. 0 = unlimited |
Step 2: Project Health Overview
Check overall project health for context:
Call MCP tool: harness_status
Parameters:
org_id: "<organization>"
project_id: "<project>"
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.
- 9d ago First seen · 209 lines · 121 tokens per session scan A 9b631e5644f4
debug-pipeline is a skill published in the GitHub repository harness/harness-skills (105 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 121 tokens to every session and 1,500 once invoked, about $0.0006 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
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…