Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
Install Install Rules
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sd0xdev/sd0x-harness install-rules --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/install-rules .claude/skills/install-rules && rm -rf skills-srcUse ~/.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/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .claude/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rulesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sd0xdev/sd0x-harness install-rules --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/install-rules .agents/skills/install-rules && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .agents/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sd0xdev/sd0x-harness install-rules --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/install-rules .cursor/skills/install-rules && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .cursor/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/install-rules--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sd0xdev/sd0x-harness install-rules --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/install-rules .gemini/skills/install-rules && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .gemini/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sd0xdev/sd0x-harness install-rulesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/install-rules .github/skills/install-rules && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .github/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill install-rules -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sd0xdev/sd0x-harness install-rules --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/install-rules .opencode/skills/install-rules && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "install-rules" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/install-rules into .opencode/skills/install-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "install-rules", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
install-rules- GitHub stars
- 192
- Token cost
- ~1.4k tokens
- SKILL.md length
- 594 words
- Files
- 1
- Skills in repo
- 89
- Repo updated
- First seen
- Licence
- MIT
At a glance
Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
- Development work in your project
- SKILL.md covers Trigger, When NOT to Use, Workflow and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Install Rules is an agent skill from sd0xdev/sd0x-harness. Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/install-rules”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, AskUserQuestion, Bash(mkdir:*), Bash(diff:*), Bash(git:*), Bash(ls:*)
What it can do on your machine
Read from SKILL.md and the folder at commit a4d4bc1. 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:
ReadGrepGlobWriteAskUserQuestionBash(mkdir:*)Bash(diff:*)Bash(git:*)Bash(ls:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Install Rules loads about 1.4k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 594 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 sd0xdev/sd0x-harness at commit a4d4bc1, republished under its MIT licence (© sd0xdev). 594 words, ~1,425 tokens.
Download SKILL.mdSave it as
.claude/skills/install-rules/SKILL.md (or your agent's skills folder).- name
- install-rules
- description
- Install plugin rules into project .claude/rules/ for persistent use without plugin loaded
- allowed-tools
- Read, Grep, Glob, Write, AskUserQuestion, Bash(mkdir:*), Bash(diff:*), Bash(git:*), Bash(ls:*)
Install Rules
Trigger
- Keywords: install rules, setup rules, copy rules, install-rules
When NOT to Use
- Installing hooks (use
/install-hooks) - Installing scripts (use
/install-scripts) - Full project setup (use
/project-setup)
Workflow
Phase 1: Locate plugin rules dir
Phase 2: Enumerate *.md, MINUS the override templates (*-project.md) — see below
Phase 2.5: Retired sweep — every name on the Retired table, checked in .claude/rules/
Phase 3: Determine install set (--all, specific names, or interactive)
Phase 3.5: Read manifest + classify (new/unchanged/modified/conflict)
Phase 4: Install (smart merge with manifest tracking)
Phase 4.5: Override templates — copy-when-absent only (never smart-merged)
Phase 4.6: Backfill CLAUDE.md references
Phase 5: Output reportManaged-set exclusion (required): *-project.md files are user-owned and must be excluded from the Phase 2 enumeration, so they never enter the manifest, the classification in Phase 3.5, or the smart merge in Phase 4. They are handled only by Phase 4.5 below. Routing them through the managed path would let --force, a conflict resolution, or an auto-upgrade rewrite a file the user owns.
Arguments
$ARGUMENTS| Argument | Description |
|---|---|
--all | Install all available rules |
--list | List available rules without installing |
--dry-run | Show what would be installed, no changes |
--force | Overwrite modified rules |
--legacy-strategy <strategy> | Handle pre-manifest installs (ask/overwrite/skip) |
--customize <rule> | Customize a project-override rule |
rule-names... | Specific rules to install |
Manifest Tracking
Uses .sd0x/install-state.json to track installed file hashes. Smart merge logic:
| Status | Action |
|---|---|
| New (not installed) | Copy |
| Unchanged (hash match) | Auto-upgrade |
| Modified by user | Skip (preserve edits) |
| Conflict (both changed) | AskUserQuestion |
| Retired (listed below; the plugin no longer ships it) | Unchanged since install (hash match) → remove the local copy, mark its manifest entry deleted: true, and drop its line from the project CLAUDE.md ## Rules block. Modified by user → keep the file, report it, change nothing |
Retired rules — files the plugin once installed and no longer ships. A retired rule is never re-copied; a user-modified copy is the user's to delete.
| Retired | Since | Its content now lives in |
|---|---|---|
fix-all-issues.md | rules-residency task 3 | rules/auto-loop.md § Fix Obligation (resident core) and the review skill's scope contract, § Fix Obligation |
framework.md | rules-residency task 3 | — (template placeholders with no consumer; nothing replaces it) |
Phase 2.5 runs on every invocation, whatever install set Phase 3 picks. A retired rule is absent
from the plugin's rules/ directory, so Phase 2's enumeration never reaches it: the sweep walks this
table instead, checks .claude/rules/<name>, and applies the Retired row above to each copy it finds
(hash against the manifest entry; no manifest entry reads as modified — kept and reported).
--list and --dry-run report what the sweep would do and change nothing.
Show full SKILL.md (252 more words)Show less
Customize Mode (--customize)
Manages *-project.md companion files for user overrides:
| Sub-flag | Action |
|---|---|
| (none) | Show section status |
--add-section | Add a new section |
--update-section <name> | Update specific section |
--reset | Regenerate from template |
Override Template Copy Contract (R8)
All three override templates are copied from rules/ on install when absent (override_templates in docs/features/rule-override-pattern/2-tech-spec.md maps auto-loop.md → auto-loop-project.md, testing.md → testing-project.md and git-workflow.md → git-workflow-project.md). This is the only install or re-install path that writes them — they are excluded from the managed set above, so no merge, upgrade, or --force reaches them. (The one other writer is the user-invoked --reset, below.)
The copy and --reset regeneration produce the live-precedence header (a live Precedence: paragraph before the first ## — HTML comments are stripped from model context, so a comment-form declaration never reaches the model), and stamp <!-- Based on: <base> @ <hash> --> with the base rule's blob hash at copy time rather than carrying the template's recorded value, so a fresh install starts at zero drift instead of inheriting whatever hash the shipped template happened to record.
An already-installed .claude/rules/*-project.md is user-owned and is never rewritten by install or re-install — including --force, which governs the managed set only. The single exception is --customize <rule> --reset, which the user invokes explicitly against a named file to regenerate it; that is a requested overwrite, not an install-time one. A legacy comment-only header is therefore reported by /claude-health S2.5 check #6 and never migrated on the user's behalf — --reset is offered as the remedy the user may choose, not an action the install path takes.
Output
## Install Rules Report
| Rule | Status | Action |
|------|--------|--------|
| auto-loop.md | unchanged | auto-upgraded |
| testing.md | user-modified | skipped |
Installed: N | Skipped: M | Conflicts: K© sd0xdev, 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/install-rules of sd0xdev/sd0x-harness.
Open the folder on GitHubat commit a4d4bc1
Compare with similar skills
Install Rules 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Install Rules this skillsd0xdev/sd0x-harness | 192 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from sd0xdev/sd0x-harness
All 89 skills in this repoAdr
sd0xdev/sd0x-harness
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…
Load PR Review
sd0xdev/sd0x-harness
Load GitHub PR review comments into AI session — analyze, triage, plan.
Next Step
sd0xdev/sd0x-harness
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.
Obsidian CLI
sd0xdev/sd0x-harness
Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.
Orchestrate
sd0xdev/sd0x-harness
Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.
PR Comment
sd0xdev/sd0x-harness
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.
Related
Categories
Questions about Install Rules
What does Install Rules do?
Install plugin rules into project .claude/rules/ for persistent use without plugin loaded. Install Rules is an agent skill from sd0xdev/sd0x-harness.
When should I use Install Rules?
Install Rules fits situations like: development work in your project.
How do I install Install Rules in Claude Code?
Run `npx skills add sd0xdev/sd0x-harness --skill install-rules -a claude-code`. Or copy the skill folder (skills/install-rules in sd0xdev/sd0x-harness) into .claude/skills/install-rules in your project. Claude Code loads it when a task matches its description.
How do I install Install Rules in Codex?
Run `npx skills add sd0xdev/sd0x-harness --skill install-rules -a codex`. Or copy the skill folder (skills/install-rules in sd0xdev/sd0x-harness) into .agents/skills/install-rules in your project. Codex loads it when a task matches its description.
Can I use Install Rules 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 sd0xdev/sd0x-harness --skill install-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/install-rules, .gemini/skills/install-rules, .github/skills/install-rules and .opencode/skills/install-rules in your project.
What does Install Rules need to run?
SKILL.md names no scripts, command-line tools or credentials: Install Rules is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, AskUserQuestion, Bash(mkdir:*), Bash(diff:*), Bash(git:*), Bash(ls:*).
Does Install Rules 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 Install Rules safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Install Rules use?
Install Rules 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 Install Rules use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Install Rules?
Skills that share tags, products or a category with Install Rules: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Install Rules?
sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 8, 2026.
Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.