ferrox-verifier
217Agent
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
Agent
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
Hook
Runs when a session starts, executing ferrox-ensure-canonical-path.js and ferrox-check-update.js via node (2 commands). From FerroxLabs/ferrox-factory.
Hook
Runs before the agent uses a tool for Write, Edit, Write, Edit, MultiEdit, Bash, mcp__com-github-github-mcp-server__merge_pull_request, mcp__com-github-github-mcp-server__push_files and mcp__com-github-github-mcp-server__create_or_update_file tool calls, executing ferrox-prompt-guard.js, ferrox-read-guard.js…
Hook
Runs after a tool call finishes for Bash, Edit, Write, MultiEdit, Agent, Task, Read, WebFetch and WebSearch tool calls, executing ferrox-context-monitor.js and ferrox-read-injection-scanner.js via node (2 commands). From FerroxLabs/ferrox-factory.
Hook
Runs when a subagent finishes, executing ferrox-context-monitor.js via node. From FerroxLabs/ferrox-factory.
Hook
Runs when the agent finishes a response, executing ferrox-context-monitor.js via node. From FerroxLabs/ferrox-factory.
Hook
Runs before the context is compacted, executing ferrox-context-monitor.js via node. From FerroxLabs/ferrox-factory.
Hook
Runs on the FileChanged event for config.json tool calls, executing ferrox-config-reload.js via node. From FerroxLabs/ferrox-factory.
Skill Claude CodeCodex
Use when building or restyling any frontend or UI surface - web pages, components, dashboards, landing pages, HTML mockups, or visual companion screens. Covers aesthetic direction, typography, layout, copy, the anti-template discipline, the design knowledge base, and the DESIGN.md contract.
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Use when starting any conversation: invoke the relevant Ferrox discipline or lifecycle workflow skill before acting, including before clarifying questions.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Something was built and you want tests covering what it promised to do.
Skill Claude CodeCodex
A step involves building an AI system and you want its design and evals pinned down first.
Skill Claude CodeCodex
You want issues found, classified, fixed, tested and committed without steering each one.
Skill Claude CodeCodex
A milestone looks done and you want it checked against what you originally asked for.
Skill Claude CodeCodex
You want every outstanding verification item across all steps gathered in one place.
Skill Claude CodeCodex
Build every remaining step by itself, discuss then plan then execute, pausing on decisions.
Skill Claude CodeCodex
You have an idea or a blank page and want to think it through. 3 silent stances, then routes.