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/promptpartner/agentsmith/harness-helpnpx skills add PromptPartner/agentsmith --skill harness-helpgit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/harness-help)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/harness-help"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/harness-help.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.00079 | $0.00524 |
| Opus 5 | $0.00039 | $0.00262 |
| Sonnet 5 | $0.00016 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
harness-help 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 today.
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.
What it actually says
Harness help — get oriented
Explain, in plain language with no jargon, what this harness does for the operator and what to do next. This is the non-coder's front door.
When this fires
"what is this harness / what does it do?" / "what are my rules?" / "which profile am I on?" / "what do I type next?" / a general "help me get started here".
Identify the target
Use the agent named by the operator or the explicit AGENTSMITH_AGENT value. Never infer the active
agent from this skill's install path: portable canonical content may be copied into a required
client adapter such as .claude/skills. Without a declared agent, explain the common rules and
label agent-specific safety configuration as unknown.
What to do (no script needed)
Read the canonical managed block in AGENTS.md and report:
- Active profile(s) — the work-type this project is tuned for (from the profile section).
- Your rules, in 3–5 bullets — the load-bearing ones (verify before done, protected main, look before you delete, be honest about what failed). Summarize; don't dump the file.
- Safety mode — when an agent is declared, read its managed native configuration and explain the effective approval and sandbox settings. Otherwise say that client-specific safety was not identified.
- What to type next — take one small task end to end. Say “verify” or “handoff”; mention an invocation prefix only when the declared client documents one.
Point to docs/01-harness-philosophy.md and docs/07-how-to-pick-a-profile.md for the why and the
profile choices. If FIRST-STEPS.md exists, point at it too.
Report
A short, friendly orientation: the selected agent when known, profile, a few rules, safety mode, and the one thing to do next. No file dumps, no jargon.
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.
- today Changed · +1 lines 6524aa645a4f
- 4d ago First seen · 38 lines · 79 tokens per session scan A 776dd936e4f4
harness-help is a skill published in the GitHub repository PromptPartner/agentsmith (185 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 524 once invoked, about $0.0004 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
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story only when the user explicitly invokes /crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
truthmark-sync
Use automatically at finish-time after functional code changes, or explicit /truthmark-sync, $truthmark-sync, or /truthmark:sync. Skip docs-only, formatting-only, behavior-preserving renames, missing config, and no-code changes. Not for doc-first realization or manual topology design.
truthmark-document
Use when the user asks to document existing implemented behavior, or Sync, Check, or Structure finds implemented behavior missing canonical truth. Not for functional-code changes, doc-first implementation, or topology repair that needs Structure.
truthmark-realize
Use when the user explicitly asks to realize Truthmark truth docs into code, including /truthmark-realize, $truthmark-realize, or /truthmark:realize. Not for syncing docs after code changes, documenting existing code, topology repair, or truth audits.