Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.
SkillScore73Maintained
Automatic
◆AI Engineer pack
Last verified 8/20/2026
What it changes
Passed 13 of 18 test cases with the skill, and 8 of 18 without it.
Specifies ~/.codex/config.toml as the configuration file path
and 3 more in the full report
6 fixed10 passed either way6 still failing0 broke
Pass-rate lift
+27 pp
Tokens
-24%
Agent turns
0%
Response time
-59%
Model gemini-3.6-flashMeasured 8/20/2026v116 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
I have skills installed across multiple agent roots beyond Codex, such as Claude and custom paths. I want to pass a parameter to inspect every discoverable skill root directory across all agents in Markdown. What exact CLI flags should be passed?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies --mode all
Missed
Passed
case-08 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md51 linessingle file
Skills Governance
Purpose
Use the bundled scanner as the source of truth for local skill inventory. Base recommendations on real directories and SKILL.md frontmatter instead of stale catalogs or memory.
When to Use
The user says they have too many skills and cannot tell what is useful.
The user wants a Codex-first keep or disable plan.
The user needs duplicate-name groups across multiple skill roots.
The user suspects imported plugin packs or mirrored skills are causing confusion.
The user wants a filesystem-backed inventory before changing skill settings.
How to Run It
Invoke the bundled scan.js from this skill directory.