agentmods.dev

forge-behavior

forge-behavior is a skill for Claude Code from luiseiman/dotforge. It costs 46 tokens per session (911 once invoked), scanned A, original, MIT.

A control for checking and changing which dotforge v3 behaviour rules are active. It can show their status, turn them on or off, and change how strict they are.

In plain words
What is it for?
Use it to inspect active behaviours, disable a rule for the current session or project, and make a rule stricter or more relaxed. It is intended for dotforge v3 projects, not v2.9 projects.
Why use it?
It removes the need to edit behaviour settings by hand when checking or adjusting rules during a session or across a project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the dotforge plugin — 25 skills, 25 commands, 7 agents, 8 hooks shipped together

not rated 8repo 9d ago A scan 46 tokens original MIT

Good fit Use it to inspect active behaviours, disable a rule for the current session or project, and make a rule stricter or more relaxed. It is intended for dotforge v3 projects, not v2.9 projects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luiseiman/dotforge/forge-behavior
View source ↗ luiseiman/dotforge
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.

Any agent
npx skills add luiseiman/dotforge --skill forge-behavior
Clone the repo
git clone --depth 1 https://github.com/luiseiman/dotforge

Made for: Claude Code.

Or install dotforge, the plugin that ships this one along with the rest of its 25 skills, 25 commands, 7 agents, 8 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for forge-behavior

README.md
[![agentmods](https://agentmods.dev/badge/skills/luiseiman/dotforge/forge-behavior/github.svg)](https://agentmods.dev/skills/luiseiman/dotforge/forge-behavior)
Your own site
<a href="https://agentmods.dev/skills/luiseiman/dotforge/forge-behavior"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/forge-behavior/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for forge-behavior

Your own site · 80×15
<a href="https://agentmods.dev/skills/luiseiman/dotforge/forge-behavior"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/forge-behavior.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00046 $0.00911
Opus 5.5 $0.00018 $0.00364
Sonnet 5.5 $0.00009 $0.00182
Haiku 4.5 $0.00005 $0.00091

Measured 1mo ago against content hash 536f51e47562, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

forge-behavior 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 1mo 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.

skills/forge-behavior/SKILL.md · 100 lines

How it starts

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

/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

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: counters, effective levels, override counts, pending_block status, and any session-scope overrides.

on / off — Toggle a behavior's active state.

  • --project (default): mutates behaviors/index.yaml. Persistent. After changing, recompile the behavior with scripts/compiler/compile.sh behaviors/<id>/behavior.yaml <output_dir> and restart Claude Code so the new hook registration takes effect.
  • --session SESSION_ID: mutates only .forge/runtime/state.json's behavior_overrides[] for that session. The compiled hook short-circuits silently when disabled. No recompile needed. Effect lasts until the session is purged by TTL.

strict / relaxed — Mutate behaviors/<id>/behavior.yaml escalation:

  • strict: halves each after threshold, minimum 1. Makes violations escalate sooner.
  • relaxed: doubles each after threshold. Makes violations escalate later.
  • Both project-scope only in v1. Session-scope strictness deferred to Phase 2 — the runtime would need to pass a strictness multiplier into forge_resolve_level, which v1 does not support.

Read the full file on GitHub · 100 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. 1mo ago First seen · 100 lines · 46 tokens per session scan A 536f51e47562

Subscribe to this mod's changes

forge-behavior is a skill published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 911 once invoked, about $0.0002 per session on Opus 5.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-31.

Building agentsClaude Codeai-codinganthropicclaude-code-agentsclaude-code-configclaude-code-hooks
Related

Other skills, from other repositories

zephermine

Creates a persisted, sectionized implementation artifact suite through research, stakeholder interviews, domain analysis, database and API design, and multi-LLM review. Use for feature or product plans consumed by downstream implementation and QA. Prefer lightweight native plan/interview workflows for small tasks; on…

Dannykkh/skill-olympus · 97 tokens

clio

A final-review and document-production workflow. It checks whether a process is ready to proceed, extracts source-based diagrams, and creates documents such as product requirements, technical documentation, and manuals.

Dannykkh/skill-olympus · 107 tokens

design-plan

A design-system planning and implementation guide for frontend projects. A design system is a shared set of visual rules, reusable components, and accessibility practices for building consistent user interfaces.

Dannykkh/skill-olympus · 108 tokens

agent-team

A guide for coordinating a team of coding agents working on one task. It covers when to split work into parallel assignments, how a lead agent coordinates them, and how to record shared knowledge.

Dannykkh/skill-olympus · 132 tokens

argos

A software inspection skill that checks an implementation against design documents such as API specifications, quality-assurance scenarios, flow diagrams, and other project specifications.

Dannykkh/skill-olympus · 89 tokens

autoresearch

A skill for improving a skill's instructions through repeated small changes and checks. It uses a 36-question checklist, keeps changes that score better, and undoes changes that do not.

Dannykkh/skill-olympus · 135 tokens