azoth-hookmode

Expose a Codex-native entrypoint for the /hookmode workflow.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-hookmode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-hookmode
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-hookmode
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-hookmode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables Codex-based users to access and control the Azoth /hookmode workflow via a dedicated, minimal entrypoint, reducing ambiguity and integration friction.

Core Features & Use Cases

  • Codex-visible entrypoint for /hookmode, preserving workflow contracts and required bindings.
  • Read and apply command contract from commands/hookmode/command.yaml and body from .claude/commands/hookmode.md.
  • Maintain user prompt arguments as ARGUMENTS and enforce the command's agent: orchestrator binding and azoth_effect: write.

Quick Start

Trigger the hookmode workflow from Codex by invoking the azoth-hookmode skill and supplying your desired ARGUMENTS.

Frequently Asked Questions about azoth-hookmode

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

FAQPage Schema
What is the hookmode workflow used for in Codex-assisted development?

The hookmode workflow provides a Codex-native entrypoint to inspect, switch, or execute command workflows. It preserves the stage rules, gate rules, evaluation rules, and the orchestrator agent binding defined in the command contract.

How do I trigger and execute the hookmode workflow from Codex?

To trigger the hookmode workflow from Codex, invoke the azoth-hookmode skill surface and supply your desired ARGUMENTS. The workflow reads the command contract from commands/hookmode/command.yaml and the body from .claude/commands/hookmode.md.

Do I need specific command files to use the hookmode entrypoint?

Yes, the hookmode entrypoint requires commands/hookmode/command.yaml and .claude/commands/hookmode.md to be present. These files define the command contract, stage rules, gate rules, and the agent orchestrator binding required for execution.

Can I pass custom user prompts to the hookmode workflow in Codex?

Yes, you can pass custom user prompts as ARGUMENTS when invoking the azoth-hookmode skill. The workflow maintains these user prompt arguments and applies them while enforcing the command's agent orchestrator binding and azoth_effect: write.

What distinguishes the azoth-hookmode skill from manually running hookmode commands?

The azoth-hookmode skill provides a dedicated, minimal Codex-visible entrypoint that reduces ambiguity and integration friction. Unlike manual execution, it automatically preserves the workflow contracts, stage rules, gate rules, and the required agent binding.

Why is my hookmode workflow not applying the correct stage and gate rules?

The hookmode workflow enforces stage rules, gate rules, and evaluation rules by reading the command contract from commands/hookmode/command.yaml. Ensure this file is intact and the agent orchestrator binding is maintained to avoid rule execution failures.