Agent skill

Cursor Backend Setup

by Chachamaru127 in Chachamaru127/claude-code-harness

Checks and configures Cursor as the implementation backend for Claude Code Harness, at user or project level, without touching shipped defaults.

MITAuto-check: notesAgent Workflows

Install Cursor Backend Setup

skills CLI
$ npx skills add Chachamaru127/claude-code-harness --skill cursor-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Chachamaru127/claude-code-harness cursor-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Chachamaru127/claude-code-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cursor-setup .claude/skills/cursor-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cursor-setup
GitHub stars
3.2k
Token cost
~1.1k tokens
SKILL.md length
160 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

Checks and configures Cursor as the implementation backend for Claude Code Harness, at user or project level, without touching shipped defaults.

  • Works in 4 steps: For --check, run → For --user-default, run → For --project-default, run → …
  • Making Cursor the default implementation backend for your user account
  • SKILL.md covers Quick Reference, Rules, Flow and Output
  • Calls bash

What it does

Running `cursor:setup` works in one of four modes. `--check` reports which backend resolves and whether the Cursor package is ready, `--user-default` makes Cursor the default for the current user, `--project-default` does the same for the current project, and `--unset` removes the setting at either scope, asking which one when the request does not say. Each mode calls helper scripts such as `setup-cursor.sh`, `set-impl-backend.sh` and `resolve-impl-backend.sh` from the Harness plugin root.

Rules keep the change local. Distribution defaults and plugin manifests stay untouched so the shipped fallback remains `claude`, and files like `~/.cursor/permissions.json`, `.cursorignore` and the Claude sandbox allowlists are treated as the user's own unless they ask for a local edit. The reply is limited to three facts: the resolved backend (claude, codex or cursor), Cursor package readiness, and the next manual step if Cursor is not ready.

When your agent uses it

  • Making Cursor the default implementation backend for your user account
  • Checking whether the Cursor plugin and agent are ready for the Harness
  • Setting or removing a project-level Cursor backend override

Example prompts

  • “Run cursor:setup --check and tell me whether Cursor is ready.”
  • “Make Cursor the default backend for this project only.”
  • “Remove my user-level Cursor default and go back to the claude fallback.”

Requirements

  • Claude Code Harness plugin with its setup-cursor.sh and set-impl-backend.sh scripts
  • Bash
  • Pre-approved tools (allowed-tools): Read, Bash

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. For --check, run
  2. For --user-default, run
  3. For --project-default, run
  4. For --unset, ask whether the target is user or project scope if not clear from the request, then run exactly one matching unset command

What it can do on your machine

Read from SKILL.md and the folder at commit 2b2b748. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cursor Backend Setup loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 160 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Chachamaru127/claude-code-harness at commit 2b2b748, republished under its MIT licence (© Chachamaru127). 160 words, ~1,141 tokens.

Download SKILL.mdSave it as .claude/skills/cursor-setup/SKILL.md (or your agent's skills folder).
name
cursor-setup
description
Configure and verify the Cursor backend for Claude Code Harness. Use when user invokes cursor:setup, wants Cursor as the local default implementation backend, or asks to check Cursor plugin/agent readiness. Distribution default remains opt-in; only local env/user settings are changed when explicitly requested.
allowed-tools
Read, Bash
description-en
Configure and verify the Cursor backend for Claude Code Harness. Use when user invokes cursor:setup, wants Cursor as the local default implementation backend…
description-ja
Claude Code Harness の Cursor backend を設定・検証するスキル。cursor:setup、Cursor を現環境の default 実装 backend にしたい、Cursor plugin/agent readiness を確認したい時に使う。配布 plugin の…
argument-hint
[--check | --user-default | --project-default | --unset]
user-invocable
true

cursor:setup - Cursor Backend Setup

Cursor backend の setup / verification 用 skill。配布 plugin の fallback は claude のままにし、現在の repo / user 環境だけ cursor default にする時に使う。

Quick Reference

bash
cursor:setup --check
cursor:setup --user-default
cursor:setup --project-default
cursor:setup --unset

Rules

  • Do not change distribution defaults or plugin manifests to make Cursor the shipped fallback.
  • Use scripts/resolve-impl-backend.sh / scripts/set-impl-backend.sh; do not infer from HARNESS_IMPL_BACKEND alone.
  • Treat ~/.cursor/permissions.json, .cursorignore, and Claude sandbox allowlists as manual/user-owned setup surfaces unless the user explicitly asks to edit a local file.

Flow

First resolve the Harness helper root. Keep the current working directory as the target project so project-scoped env.local writes still land in the user's repo:

bash
HARNESS_PLUGIN_ROOT="${HARNESS_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"
if [ -z "$HARNESS_PLUGIN_ROOT" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ]; then
  probe="$(cd "${CLAUDE_SKILL_DIR}" && pwd)"
  while [ "$probe" != "/" ] && [ ! -d "$probe/scripts" ]; do
    probe="$(cd "$probe/.." && pwd)"
  done
  [ -d "$probe/scripts" ] && HARNESS_PLUGIN_ROOT="$probe"
fi
if [ -z "$HARNESS_PLUGIN_ROOT" ]; then
  echo "ERROR: HARNESS_PLUGIN_ROOT is not set and could not be derived from CLAUDE_PLUGIN_ROOT or CLAUDE_SKILL_DIR" >&2
  exit 2
fi
  1. For --check, run:

    bash
    bash "${HARNESS_PLUGIN_ROOT}/scripts/setup-cursor.sh" --check
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
    bash "${HARNESS_PLUGIN_ROOT}/scripts/resolve-impl-backend.sh" --role worker
    CURSOR_AGENT_BIN="${CURSOR_AGENT_BIN:-}"
    if [ -z "$CURSOR_AGENT_BIN" ]; then
      # `agent`(公式の新表記)→ `cursor-agent`(legacy alias)の順に探す。
      # `agent` は汎用的な名前なので、symlink 解決後の実パスの「成分」に
      # cursor-agent が完全一致で現れる場合だけ採用する(部分文字列一致だと
      # /x/cursor-agent-not-really/agent のようなディレクトリ名で突破される)。
      for _c in agent cursor-agent; do
        _p="$(command -v "$_c" 2>/dev/null)" || continue
        [ -n "$_p" ] || continue
        _r="$(realpath "$_p" 2>/dev/null || readlink -f "$_p" 2>/dev/null || echo "$_p")"
        case "/$_r/" in */cursor-agent/*) CURSOR_AGENT_BIN="$_p"; break ;; esac
      done
      if [ -z "$CURSOR_AGENT_BIN" ] && [ -x "$HOME/.local/bin/cursor-agent" ]; then
        CURSOR_AGENT_BIN="$HOME/.local/bin/cursor-agent"
      fi
    fi
    if [ -z "$CURSOR_AGENT_BIN" ]; then
      echo "ERROR: cursor-agent not found in PATH or $HOME/.local/bin" >&2
      exit 3
    fi
    "$CURSOR_AGENT_BIN" --version
  2. For --user-default, run:

    bash
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --user cursor
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
  3. For --project-default, run:

    bash
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" cursor
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --show
  4. For --unset, ask whether the target is user or project scope if not clear from the request, then run exactly one matching unset command:

    Project scope:

    bash
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --unset

    User scope:

    bash
    bash "${HARNESS_PLUGIN_ROOT}/scripts/set-impl-backend.sh" --unset --user

Output

Report three facts only:

  • resolved backend (claude / codex / cursor)
  • Cursor package readiness (setup-cursor.sh --check)
  • next manual step if Cursor is not ready

© Chachamaru127, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cursor-setup of Chachamaru127/claude-code-harness.

Open the folder on GitHubat commit 2b2b748

Compare with similar skills

Cursor Backend Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cursor Backend Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cursor Backend Setup this skillChachamaru127/claude-code-harness3.2k—~1.1kAutomated safety check: NotesMIT
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k10 repos~3.5kAutomated safety check: PassMIT
Plugin Settings Patternanthropics/claude-plugins-official37k7 repos~3kAutomated safety check: PassApache-2.0
MCP Integration for Pluginsanthropics/claude-plugins-official37k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 10 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    37k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    37k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    37k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

More from Chachamaru127/claude-code-harness

All 25 skills in this repo
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check: notes
  • Cursor Composer Task Delegate

    Chachamaru127/claude-code-harness

    Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.

    3.2k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check: notes
  • Acceptance Demo Generator

    Chachamaru127/claude-code-harness

    Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.

    3.2k GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Long-Running Task Loop

    Chachamaru127/claude-code-harness

    Repeats a long task as a series of scheduled wake-ups, each re-entering with fresh context and calling harness-work for one task per cycle.

    3.2k GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Plan

    Chachamaru127/claude-code-harness

    Creates and maintains Plans.md task plans with a spec delta, updates task markers and syncs plan progress with the implementation.

    3.2k GitHub stars~3.7k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Release

    Chachamaru127/claude-code-harness

    Runs a release for any project that keeps a Keep a Changelog file on GitHub, from version bump to merge, tag and GitHub Release after a single approval.

    3.2k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check: notes

Categories

Questions about Cursor Backend Setup

What does Cursor Backend Setup do?

Checks and configures Cursor as the implementation backend for Claude Code Harness, at user or project level, without touching shipped defaults. Running `cursor:setup` works in one of four modes. `--check` reports which backend resolves and whether the Cursor package is ready, `--user-default` makes Cursor the default for the current user, `--project-default` does the same for the current project, and `--unset` removes the setting at either scope, asking which one when the request does not say.

When should I use Cursor Backend Setup?

Cursor Backend Setup fits situations like: making Cursor the default implementation backend for your user account; checking whether the Cursor plugin and agent are ready for the Harness; setting or removing a project-level Cursor backend override.

How do I install Cursor Backend Setup in Claude Code?

Run `npx skills add Chachamaru127/claude-code-harness --skill cursor-setup -a claude-code`. Or copy the skill folder (skills/cursor-setup in Chachamaru127/claude-code-harness) into .claude/skills/cursor-setup in your project. Claude Code loads it when a task matches its description.

How do I install Cursor Backend Setup in Codex?

Run `npx skills add Chachamaru127/claude-code-harness --skill cursor-setup -a codex`. Or copy the skill folder (skills/cursor-setup in Chachamaru127/claude-code-harness) into .agents/skills/cursor-setup in your project. Codex loads it when a task matches its description.

Can I use Cursor Backend Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Chachamaru127/claude-code-harness --skill cursor-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cursor-setup, .gemini/skills/cursor-setup, .github/skills/cursor-setup and .opencode/skills/cursor-setup in your project.

What does Cursor Backend Setup need to run?

Going by SKILL.md and its folder, Cursor Backend Setup needs the command-line tools its instructions call (bash). Our summary lists: Claude Code Harness plugin with its setup-cursor.sh and set-impl-backend.sh scripts; Bash. Its frontmatter pre-approves these tools: Read, Bash.

Does Cursor Backend Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cursor Backend Setup safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Cursor Backend Setup use?

Cursor Backend Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cursor Backend Setup use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cursor Backend Setup?

Skills that share tags, products or a category with Cursor Backend Setup: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 37k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cursor Backend Setup?

Chachamaru127 (a GitHub user) maintains it in Chachamaru127/claude-code-harness, which has 3,153 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 5, 2026.

Source: Chachamaru127/claude-code-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.