Saucebox Registry
← Browse

@ancienttwo/repo-harness-chatgpt

A

Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.

skillclaude

Install

agr install @ancienttwo/repo-harness-chatgpt --target claude

Writes 1 file into .claude/skills/, pinned to git-38581cf2.

  • .claude/skills/repo-harness-chatgpt/SKILL.md

Document

name: repo-harness-chatgpt description: Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence. when_to_use: "repo-harness-chatgpt, ChatGPT Web consult, GPT Pro consult, gptpro, browser GPT, ChatGPT MCP Connector, ChatGPT bridge, MCP read-back, GPT Pro delegate, delegate to ChatGPT, 外包给 GPT"

repo-harness-chatgpt

Canonical rule owner for every repo-harness ChatGPT integration surface: Oracle browser consult, session continuation, MCP Connector/bridge setup and operation, and MCP invocation read-back evidence. Discoverable only after explicit ChatGPT setup; never implied by either install profile. Router-only: mode protocol lives under references/.

Mode Selection

  • First-time Oracle browser or MCP Connector configuration -> references/setup.md.
  • Start a new local -> ChatGPT Web browser consult -> references/consult.md.
  • Continue, read, or clean up a saved browser session -> references/continue.md.
  • Verify or accept a ChatGPT MCP tool call as real evidence -> references/read-back.md.
  • Operate the MCP Connector bridge (planner/executor/orchestrator/coding) -> references/bridge.md.
  • Delegate a self-contained task to GPT Pro and independently accept the result -> references/delegate.md.

Boundaries

  • Product planning never implies this package; ChatGPT discovery requires explicit setup.
  • Never request or handle ChatGPT passwords, 2FA codes, cookies, browser storage, or session tokens; login/captcha/SSO stop and hand back to the user.
  • Setup, consult, and bridge modes share these safety rules by reference; none shares secrets, auth state, or tokens with another mode.
  • Consult stays planning/review/critique only, never the code-edit executor; delegate is the sole approved path for code deliverables, and GPT Pro still never executes edits.
  • A missing or unreadable canonical reference fails the calling command closed; it never synthesizes replacement prose.
  • Do not enable remote CDP or an orchestrator dev runner unless the user explicitly asks and the boundary is documented.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-38581cf2d8e02026-07-31