flowai-skill-engineer-hook

Configure cross-IDE agent hooks to block, modify, or confirm actions.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/korchasa/foxcode --skill flowai-skill-engineer-hook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowai-skill-engineer-hook
Source: https://github.com/korchasa/foxcode/tree/main/.claude/skills/flowai-skill-engineer-hook
Command: npx skills add https://github.com/korchasa/foxcode --skill flowai-skill-engineer-hook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Designing and configuring event hooks (or plugins) to manage agent behavior, commands, file reads/writes, and tool usage across IDEs (Cursor, Claude Code, and OpenCode), enabling consistent governance, auditing, and safety checks.

Core Features & Use Cases

  • Intercept, evaluate, and apply rules to agent actions: allow, block (with explanation), request confirmation, or modify input data.
  • Provide a unified approach for creating and configuring hooks/plugins across Cursor, Claude Code, and OpenCode, including templates and references.
  • Use case: implement a security hook that blocks dangerous commands or enforces coding standards during agent interactions.

Quick Start

Create your first hook entry by wiring a new hook into an event using the IDE references.

Frequently Asked Questions about flowai-skill-engineer-hook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure agent hooks to block dangerous commands in Claude Code?

To configure agent hooks in Claude Code, you wire a new hook entry into a specific event using the provided IDE references. This allows you to intercept, evaluate, and apply rules to block dangerous commands or enforce coding standards during automated agent interactions.

Can I use the same hook configuration across Cursor, Claude Code, and OpenCode?

Yes, you can use a unified approach for creating and configuring hooks across Cursor, Claude Code, and OpenCode. The skill provides IDE detection, 4 hook types, 18 events mapping, and example templates to ensure consistent governance and safety checks across these different environments.

What are agent hooks and when do I need them for automated workflows?

Agent hooks are event plugins that manage agent behavior, commands, file reads/writes, and tool usage within IDEs. You need them to apply consistent governance, auditing, and safety checks, allowing you to allow, block, request confirmation, or modify input data during automated workflows.

How do I create a new hook entry to intercept file writes in Cursor?

You create a new hook entry by wiring a new hook into an event using the IDE references and the provided shell script template. This process enables you to script custom logic to intercept, evaluate, and modify input data for file writes or other agent actions in Cursor.

Does this approach support modifying input data before an agent action executes?

Yes, the hook configuration supports scripting logic to modify input data before an action executes. Alongside allowing or blocking actions with an explanation, you can intercept and evaluate agent commands or file operations to dynamically alter their input data across supported IDE environments.