Agent skill

forge-behavior

Manage dotforge v3 behavior governance — view status, toggle behaviors, adjust strictness. Use when the user asks about active behaviors, wants to disable one for the current session, or adjust escalation thresholds.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill forge-behavior --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/agent/forge-behavior/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /forge behavior Thin wrapper around `scripts/forge-behavior/cli.sh`. Dispatches behavior governance actions. This skill is part of dotforge v3 (Phase 1 of behavior governance) and should only be used inside dotforge itself or projects that have adopted v3 — not on v2.9 projects. ## When to use Invoke this skill when the user asks any of: - "What behaviors are active?" - "What's the counter on search-first?" - "Disable search-first for this session" - "Turn off the nudge on writes" - "Make search-first stricter / more relaxed" Do NOT invoke this skill for v2.9 configuration tasks (use `/forge audit`, `/forge sync`, etc.) or for behaviors that have not yet been catalogued (Phase 1 only ships search-first). ## Actions ```bash scripts/forge-behavior/cli.sh status [--session SESSION_ID] scripts/forge-behavior/cli.sh on <behavior_id> [--project | --session SESSION_ID] scripts/forge-behavior/cli.sh off <behavior_id> [--project | --session SESSION_ID] scripts/forge-behavior/cli.sh strict <behavior_id> scripts/forge-behavior/cli.sh relaxed <behavior_id> ``` **status** — Print the current catalogue (`behaviors/index.yaml`) plus a per-session summary from `.forge/runtime/state.json`: counte

What's inside
Steps it walks through
  1. When to use
  2. Actions
  3. Preconditions
  4. Scope matrix
  5. Example flows
  6. Notes
Ships with 1 file
  • metadata.json
Commands it runs
scripts/forge-behavior/cli.sh status [--session SESSION_ID]
scripts/forge-behavior/cli.sh on  <behavior_id> [--project | --session SESSION_ID]
scripts/forge-behavior/cli.sh off <behavior_id> [--project | --session SESSION_ID]
scripts/forge-behavior/cli.sh strict  <behavior_id>
scripts/forge-behavior/cli.sh relaxed <behavior_id>
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the forge-behavior skill do?

Manage dotforge v3 behavior governance — view status, toggle behaviors, adjust strictness. Use when the user asks about active behaviors, wants to disable one for the current session, or adjust escalation thresholds.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill forge-behavior --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.