If you run this workflow, ask Fable to make codex the workhorse. https://github.com/steipete/agent-scripts/blob/main/skills/codex-first/SKILL.md…

steipete/agent-scripts

Source: https://github.com/steipete/agent-scripts

Agent Scripts

Shared agent instructions, skills, and small portable helpers for Peter’s local workspaces.

This repo is the canonical place for:

• AGENTS.MD: shared hard rules for Codex/Claude-style agents
• skills/: reusable workflow skills, including repo-owned skills exposed by symlink
• scripts/: dependency-light helpers used across projects
• hooks/: local guardrails such as skill validation

Skills

Skills are the main routing layer. Each skills/<name>/SKILL.md has YAML front matter:

---
name: skill-name
description: "Short generic trigger phrase."
---

Rules:

• Keep descriptions short and generic; optimize for routing, not documentation.
• Keep skill bodies terse and operational.
• Prefer helper scripts under skills/<name>/scripts/ when a workflow has repeatable commands.
• Validate after edits: scripts/validate-skills.
• Quote description in front matter.

Global discovery is built by scripts/sync-skills (idempotent; run on every Mac after cloning or adding skills):

• Codex scans nested dirs, so it gets whole-root links: ~/.codex/skills/agent-scripts -> ~/Projects/agent-scripts/skills, ~/.codex/skills/manager -> ~/Projects/manager/skills.
• Claude Code loads only ~/.claude/skills/<name>/SKILL.md (exactly one level deep; per-entry symlinks are followed, category subfolders are not scanned — verified on 2.1.197). It gets a flat per-skill link mirror covering both repos plus machine-local ~/.codex/skills/<name> extras.
• Name collisions resolve agent-scripts > manager > codex-local; the script prints skipped duplicates and prunes broken/stale managed links.

Shared personal skills live as real folders in skills/. Public OpenClaw shared skills live in ../agent-skills and are exposed here with tracked relative symlinks. Repo-owned skills stay canonical in their repo and are exposed here the same way, for example:

skills/autoreview -> ../../agent-skills/skills/autoreview
skills/discrawl -> ../../discrawl/.agents/skills/discrawl

Current symlinked repo-owned skills include birdclaw, discrawl, gog, imsg, slacrawl, wacli, and wacrawl.

Agent Instructions

Shared hard rules live in AGENTS.MD.

Global setup (also maintained by scripts/sync-skills; Claude Code reads CLAUDE.md only, so it links to the shared AGENTS.MD):

• ~/.codex/AGENTS.md -> ~/Projects/agent-scripts/AGENTS.MD
• ~/.claude/CLAUDE.md -> ~/Projects/agent-scripts/AGENTS.MD
• ~/.claude/AGENTS.md -> ~/Projects/agent-scripts/AGENTS.MD

Downstream repos should use a pointer-style AGENTS.MD:

READ ~/Projects/agent-scripts/AGENTS.MD BEFORE ANYTHING (skip if missing).

Repo-specific rules go below that pointer. Do not copy the shared blocks into downstream repos.

Helpers

scripts/committer

• Stages exactly the listed files.
• Enforces a non-empty commit message.
• Runs skill validation before committing.

scripts/sync-skills

• Builds the per-machine skill mirror: Codex whole-root links, Claude flat per-skill links, shared AGENTS.MD pointers.
• Idempotent; prints changes only, prunes broken/stale managed links, never clobbers real files.

scripts/validate-skills

• Checks every skills/*/SKILL.md.
• Verifies YAML front matter plus required name and description.
• Enable as a local hook with git config core.hooksPath hooks.

scripts/docs-list.ts

• Walks docs/.
• Enforces summary and read_when front matter.
• Prints onboarding summaries for repos that wire it in.

scripts/browser-tools.ts

• Standalone Chrome DevTools helper.
• Common commands: start --profile, nav <url>, eval '<js>', screenshot, console, network, search --content "<query>", content <url>, inspect, kill --all --force.
• Build optional binary with bun build scripts/browser-tools.ts --compile --target bun --outfile bin/browser-tools.

Syncing

Treat this repo as canonical for shared agent rules and portable helper scripts.

When syncing downstream repos:

• Pull latest here first.
• Ensure each target repo starts with the pointer-style AGENTS.MD.
• Preserve repo-local rules below the pointer.
• Copy helper changes both directions only when the helper is meant to stay byte-identical.
• Keep scripts dependency-free and portable; no repo-specific imports or path aliases.

For submodules, repeat the pointer check inside each subrepo, push those changes, then bump submodule SHAs in the parent repo.

ClaudeDevs (@ClaudeDevs): A few patterns we frequently use with Fable 5:

Use Fable 5 as an “advisor.”

An executor (Sonnet 5) calls Fable 5 for guidance.

Most tokens are billed at the lower executor rate.