set-default-ruleset

A command for configuring GitHub branch protection rulesets, which control what must happen before code can be merged into a protected branch.

In plain words
What is it for?
Use it to inspect the repository, available GitHub Actions checks, and existing rulesets, then create or update protection requirements.
Why use it?
It helps prevent unreviewed or failing code from being merged into the repository’s default branch.

Command

Install

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.

agentmods
npx agentmods add commands/jeffh/claude-plugins/set-default-ruleset
Clone the repo
git clone --depth 1 https://github.com/jeffh/claude-plugins
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.01270
Opus 5 $0.00005 $0.00635
Sonnet 5 $0.00002 $0.00254
Haiku 4.5 $0.00001 $0.00127

Measured 2d ago against content hash 7d2bc6dce3cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

set-default-ruleset 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 2d 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.

gh/commands/set-default-ruleset.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set GitHub Branch Ruleset

You are tasked with creating or updating a GitHub branch ruleset to protect the default branch.

Process

1. Get Repository Information

# Get repository details
gh repo view --json name,owner,defaultBranchRef

# Get existing rulesets (if any)
gh api repos/{owner}/{repo}/rulesets --jq '.[] | {id, name, enforcement}'

2. Check Available GitHub Actions

Run this to discover available workflow job names that can be used as status checks:

# List workflow files
gh api repos/{owner}/{repo}/actions/workflows --jq '.workflows[] | {name: .name, path: .path}'

# For each workflow, you can inspect jobs by reading the workflow file

Also check the repository's .github/workflows/ directory to understand job names.

3. Ask User for Configuration

Use AskUserQuestion to ask the user:

Question 1: Protection Type

  • "Use Status Checks (require CI jobs to pass)" - Default, recommended if GitHub Actions exist
  • "Use Code Scanning Results (require security analysis)" - Use GitHub Advanced Security code scanning

If Status Checks selected and GitHub Actions exist:

Question 2: Which Status Checks to Require Present the discovered workflow job names and ask which ones to require. Common patterns:

  • Build/Test jobs (e.g., "Test and Build", "CI")
  • Lint/Format jobs (e.g., "Format and Lint", "Lint")

If no GitHub Actions exist: Inform the user that no GitHub Actions were found, so status checks will be skipped. The ruleset will only enforce deletion and non-fast-forward rules.

4. Create the Ruleset

Use the GitHub API to create the ruleset:

gh api repos/{owner}/{repo}/rulesets \
  --method POST \
  --input - << 'EOF'
{
  "name": "Protect default branch",
  "target": "branch",
  "enforcement": "active",
  "bypass_actors": [],
  "conditions": {
    "ref_name": {
      "exclude": [],
      "include": ["~DEFAULT_BRANCH"]
    }
  },
  "rules": [
    {
      "type": "deletion"
    },
    {
      "type": "non_fast_forward"
    },
    {
      "type": "required_status_checks",
      "parameters": {
        "do_not_enforce_on_create": false,
        "strict_required_status_checks_policy": false,
        "required_status_checks": [
          {
            "context": "Format and Lint",
            "integration_id": 15368
          },
          {
            "context": "Test and Build",
            "integration_id": 15368
          }
        ]
      }
    }
  ]
}
EOF

Read the full file on GitHub · 207 lines

Changes

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.

  1. 2d ago First seen · 207 lines · 11 tokens per session scan A 7d2bc6dce3cd

Subscribe to this mod's changes

set-default-ruleset is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,270 once invoked, about $0.0001 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.