steipete/agent-scripts is a open-source project on GitHub, written primarily in Shell. It has 7.4k stars. Scripts for agents, shared between my repositories.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
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.
Real destination files and directories are preserved. A real Claude skill directory with a Codex backlink to that same directory satisfies local ownership; other real destination conflicts are reported and make sync fail.
For the specific legacy topology ~/.claude/skills/NAME/NAME -> ~/.codex/skills/NAME -> ~/.claude/skills/NAME, invoke the sync owner directly with an explicit allowlist:
This mode validates every candidate before unlinking only the extra nested leaves. It preserves the real skill directories, assets, and valid Codex backlinks, and exits before creating roots, building mirrors, pruning, or touching instruction pointers. Names must start with an ASCII letter or digit and contain only letters, digits, ., _, or -; duplicates, missing names, and unknown arguments are rejected. A missing nested leaf is a no-op only with the expected surrounding topology. Redirected/inaccessible roots, unexpected objects or literal targets, and changed directory/link identities cause refusal. Rechecks before each unlink are not atomic concurrency protection; a later error stops the batch and reports removals already completed, without rollback.
The read-only skills/fleet-maintenance/scripts/agent-skill-links-audit.sh reports same-name nested ancestor loops as reason=nested-self-link. This is narrow detection, not an exhaustive graph validator. Its --repair remains a broad sync through ~/Projects/agent-scripts/scripts/sync-skills; it is not the scoped repair above. Run scripts/test-sync-skills for isolated fixture coverage; scripts/test-sync-skills --recurrence-only /absolute/path/to/old-sync-skills runs the unchanged recurrence assertion against an original helper.
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:
Current symlinked repo-owned skills include birdclaw, discrawl, gog, imsg, peekaboo, slacrawl, wacli, and wacrawl.
Keep ~/Projects/peekaboo cloned and current before syncing the Peekaboo skill. Its skills/peekaboo/SKILL.md owns command, permission, capture, and interaction guidance; edit that source instead of adding another copy here. After updating both repositories, run scripts/sync-skills and verify the Peekaboo skill resolves through the Codex and Claude mirrors.
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):
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/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.
No arguments runs ordinary sync; --help prints usage. Only the scoped --repair-nested-self-links mode accepts --dry-run.
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.
content and search fail on navigation errors; a loaded article remains readable when only network idle times out. Individual search --content failures are reported per result.
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.
Releases
See RELEASING.md for the signed-tag GitHub release workflow and its no-publish rehearsal.
Yes — steipete/agent-scripts ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/steipete/agent-scripts.
What is steipete/agent-scripts?
steipete/agent-scripts (steipete/agent-scripts) is a Shell project on GitHub. From the project's own README: Scripts for agents, shared between my repositories.
What license does steipete/agent-scripts use?
steipete/agent-scripts is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where can I see steipete/agent-scripts in action?
The project maintains a homepage at https://steipete.me. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about steipete/agent-scripts?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/steipete/agent-scripts is the definitive source.
Read full README in the tab above.
Curious whether agent-scripts is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about agent-scripts.
/agent-scripts