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 commands/pierry/harness-kit/golden-pathgit clone --depth 1 https://github.com/Pierry/harness-kitWrote 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/commands/pierry/harness-kit/golden-path)<a href="https://agentmods.dev/commands/pierry/harness-kit/golden-path"><img src="https://agentmods.dev/badge/commands/pierry/harness-kit/golden-path.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.00040 | $0.01074 |
| Opus 5 | $0.00020 | $0.00537 |
| Sonnet 5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
golden-path 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golden path. Idea → merged PR. Paved, opinionated, supported. The recommended way; not the only way (step off any time, see Detours).
Full reference: docs/GOLDEN-PATH.md.
Flags
Passed through to the SSE half (/sse:run):
--local: stop after/sse:test, no PR. Dev + test locally.--sdd: spec-driven loop variant (plan once, dev↔test↔eval until PRP spec met). Local only.--no-monitor: PR opens, skip auto merge-watch.
Steps
- Invoke
/product-manager:run. Drafts PRD → PRP. Wait for approval markers on both. Follow.claude/agents/product-manager/guides/pipeline.md. - On PRP approval, invoke
/sse:runwith any flags passed to/golden-path. Runs plan → dev → test → pr → monitor. Follow.claude/agents/staff-software-engineer/guides/pipeline.md. - Return the combined summary.
Reuse the same feature_id across both halves so artifacts land under one name. The status
bar tracks all six stages (full-run shape; .claude/hooks/pipeline-prompt.sh records intent).
Detours
Golden path is optional. Run any stage solo instead: /product-manager:prd | :prp,
/sse:plan | :dev | :test | :pr, /sse:run --local, /sse:sdd. Resume with
/pipeline:continue, abandon with /pipeline:reset. Same sensors, same evals, same artifacts.
Return format
Name every sensor, eval, guide that ran. Generic summaries not acceptable, list specifics so user sees what was checked and loaded. Concatenate the PM and SSE return blocks:
Golden path complete. Idea → merged PR.
PRD: .claude/runtime/outputs/pm/prd/{path}
sensors: prd-structure ok, prd-acceptance-criteria ok ({sub-checks})
eval: prd-quality {score}/10, prd-readiness {score}/10 (attempts: N)
guides: product-guidelines.md, prd-guidelines.md, writing-style.md, templates/prd.md
refs: business-info.md, squads/{squad}/context.md
PRP: .claude/runtime/outputs/pm/prp/{path}
sensors: prp-structure ok, prp-context-quality ok, prp-links ok
eval: prp-quality {score}/10, prp-context-readiness {score}/10 (attempts: N)
guides: prp-guidelines.md, writing-style.md, templates/prp.md
refs: prd/{feature_id}.md, target repo paths probed
Plan: .claude/runtime/outputs/sse/plan/{path}
sensors: {sensor-name} ok ({sub-check, ...}), {sensor-name} ok
eval: {eval-name} {score}/10 (attempts: N)
guides: {guide-1.md}, {guide-2.md}, skills/{area}/SKILL.md
refs: prp/{feature_id}.md, conventions/{area}.md
Dev: branch {branch}
files changed: N
commits: N ({short-sha}, ...)
sensors: code-conventions ok, test-coverage ok
guides: coding-style.md, commit-style.md, skills/{area}/SKILL.md
refs: plan/{feature_id}.md, conventions/{area}.md
Test: .claude/runtime/outputs/sse/test/{path}
command: {detected-test-command}
passed: N, failed: M
duration: {seconds}s
PR: {url}
title: {title}
draft: yes|no
guides: commit-style.md
refs: plan/{feature_id}.md, dev/{feature_id}.md
Monitor: {armed, first check in 3min, escalates to 30min cap | skipped, reason}
Tokens: outputs/tokens/{feature_id}.json
totals: in={N} out={N} cache_r={N}
phases: prd-*, prp-*, plan-*, dev-*, test-*, pr-*
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.
- 3d ago First seen · 91 lines · 40 tokens per session scan A 92104634bfc3
golden-path is a command published in the GitHub repository Pierry/harness-kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,074 once invoked, about $0.0002 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-31.
Other commands, from other repositories
linkedin-growth-config
Adjust linkedin-growth account settings — daily invite limit, schedule time, pending threshold, pause/resume — or edit the ICP qualification prompt.
linkedin-growth-import
Import leads from a LinkedIn / Sales Navigator search into the pipeline — search, qualify against the ICP, dedupe, and store with round-robin assignment.
linkedin-growth-setup
Onboard the linkedin-growth pipeline — check prerequisites, connect LinkedIn accounts, register them, and install the scheduler.
linkedin-growth-status
Show the linkedin-growth dashboard — lead counts by status, invites left today, pending older than the threshold, recent errors, and recent imports.
pseo-dfs-pull
Use when: kullanıcı "DataForSEO çek", "DFS pull", "keyword overview", "search volume DFS", "dfs ingestion" der ya da /pseo-dfs-pull çağırırsa. Also use when: aktif projenin keyword listesi var, DFS bütçesi (project.config.dataforseo.budgetcreditsperday) yeterli; staging-only (Phase 8 cluster-map konsume eder). Do not…
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.