How do I install the Ferrox Config skill?

Run npx skillmds@latest add ferroxlabs/ferrox-config in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ferrox Config skill do?

You want to change how Ferrox behaves. Workflow toggles, advanced knobs, integrations It is listed under Productivity on SkillMD.

Is Ferrox Config safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ferrox Config?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ferrox Config free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ferrox Config?

FerroxLabs (@ferroxlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ferrox Config by ferroxlabs — Agent Skill

Name: Ferrox Config
Author: FerroxLabs

File contents

Mode routing:

default (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow
--advanced: Power-user knobs (planning tuning, timeouts, branch templates, cross-AI execution) → settings-advanced workflow
--integrations: Third-party API keys, code-review CLI routing, agent-skill injection → settings-integrations workflow
--profile : Switch model profile (quality|balanced|budget|inherit) → set-profile (inline)

Flag	Action	Workflow
(none)	Interactive 5-question common-case config prompt	settings
--advanced	Power-user knobs: planning, execution, discussion, cross-AI, git, runtime	settings-advanced
--integrations	API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills	settings-integrations
--profile <name>	Switch model profile without interactive prompt	ferrox-tools query config-set-model-profile

Parse the first token of $ARGUMENTS:

If it is --advanced: strip the flag, execute settings-advanced workflow
If it is --integrations: strip the flag, execute settings-integrations workflow
If it starts with --profile: extract the profile name (remainder after --profile), then:
1. Verify ferrox-tools is on PATH via command -v ferrox-tools; if absent, emit the install hint Install Ferrox via 'npm i -g ferrox-core' and stop.
2. Run: ferrox-tools query config-set-model-profile <profile-name> --raw and display the output verbatim.
Otherwise: execute settings workflow (no argument needed)

---name: ferrox-configdescription: You want to change how Ferrox behaves. Workflow toggles, advanced knobs, integrations---<objective>Configure Ferrox settings interactively with a single consolidated command.Mode routing:- **default** (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow- **--advanced**: Power-user knobs (planning tuning, timeouts, branch templates, cross-AI execution) → settings-advanced workflow- **--integrations**: Third-party API keys, code-review CLI routing, agent-skill injection → settings-integrations workflow- **--profile <name>**: Switch model profile (quality|balanced|budget|inherit) → set-profile (inline)</objective><routing>| Flag | Action | Workflow ||------|--------|----------|| (none) | Interactive 5-question common-case config prompt | settings || --advanced | Power-user knobs: planning, execution, discussion, cross-AI, git, runtime | settings-advanced || --integrations | API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills | settings-integrations || --profile <name> | Switch model profile without interactive prompt | ferrox-tools query config-set-model-profile |</routing><execution_context>@~/.claude/ferrox-core/workflows/settings.md@~/.claude/ferrox-core/workflows/settings-advanced.md@~/.claude/ferrox-core/workflows/settings-integrations.md</execution_context><context>Arguments: $ARGUMENTSParse the first token of $ARGUMENTS:- If it is `--advanced`: strip the flag, execute settings-advanced workflow- If it is `--integrations`: strip the flag, execute settings-integrations workflow- If it starts with `--profile`: extract the profile name (remainder after `--profile`), then: 1. Verify `ferrox-tools` is on PATH via `command -v ferrox-tools`; if absent, emit the install hint `Install Ferrox via 'npm i -g ferrox-core'` and stop. 2. Run: `ferrox-tools query config-set-model-profile <profile-name> --raw` and display the output verbatim.- Otherwise: execute settings workflow (no argument needed)</context><process>1. Parse the leading flag (if any) from $ARGUMENTS.2. Load and execute the appropriate workflow end-to-end, or run the inline SDK command for --profile.3. Preserve all workflow gates from the target workflow.</process>

Frequently asked questions

Ferrox Config