By ArtMin96
Behavioral steering via modular hooks: anti-sycophancy, anti-false-claims, destructive command blocking, self-review enforcement, numeric length anchors, scope discipline, minimal change enforcement, plan discipline
Audit the current session for behavioral rule violations. Use when asked to review session discipline, check for sycophancy, or evaluate behavioral compliance.
Create a task scope before starting work. Defines boundaries, acceptance criteria, and file limits to prevent scope creep. Use before any non-trivial task.
Set a message budget for the current task. Forces efficiency by tracking progress against budget. Use when you want focused, fast work.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Orchestration patterns: task routing, explore-plan-implement cycle, daily rituals
Execution trace collection, analysis, and harness evolution. Stores structured JSONL traces for pattern detection and failure-driven improvement.
Evaluator-optimizer pattern: adversarial review, verification, static analysis gates, postmortems
Context management: progressive pressure tracking, session handoffs, drift detection, edit safety, large-file warnings, plan mode hooks, MCP monitoring, prompt budget awareness
Multi-agent decomposition: planner/generator/reviewer triad with tool-isolated capability boundaries
npx claudepluginhub artmin96/forge-studio --plugin behavioral-coreThe mentor framework for Claude Code: a self-contained process layer with per-session modes, a work-item lifecycle with a hard Definition of Done, budget-aware autonomy, visual verification, and safety rules that travel into every subagent
Enforces orchestrator context window discipline via PreToolUse hooks and rules. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that should be delegated, and bypassing delegation with 'small change' rationalizations. Install to structurally prevent investigation escalation anti-patterns.
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Behavioral guardrails for Claude Code agents. Nine battle-tested rules (no-guessing, no-stalling, no-preference-asking, no-false-completion, no-skipping, no-dismissing, no-cosmetic, no-caveats, no-flagging) enforced via a Stop hook bash script. Includes analyze, install, test, and update skills for data-driven tuning.
Battle-tested configuration system for Claude Code agents: 28 architectural principles (incl. P-28 Feature-Layer Architecture for project-knowledge-as-a-navigable-tree), 19 safety hooks, 23 skills (incl. /layer-new + /feature-new for ULTRAPACK-style feature narratives), 16 alternative comparisons, 12 templates (incl. extended kb-skeleton with docs/layers/), diagnostic scripts (incl. build_kb_graph.py + validate_kb_links.py). Pairs with mclaude for multi-session coordination.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems