Agent Scripts
github.com/steipete/agent-scripts- Category
- AI Agents
- Rank
- No. 812Tools index
Previous survey · No. 807 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- @steipete
- GitHub
- 6.6k stars
- Latest release
- 0.12.0
- Date
About
Agent Scripts is a personal but public repository that centralizes one developer's AI-agent configuration: shared agent rules in AGENTS.MD, reusable workflow skills defined as Markdown files with YAML front matter, and portable helper scripts. A sync step symlinks those definitions into place for both Codex and Claude Code, which expect different directory layouts, and validation hooks check skill integrity before they propagate to downstream repos and other machines.
What it does
Agent Scripts acts as a central control layer for several coding workspaces. It routes reusable skills into Codex and Claude Code through managed links, shares common operating rules, validates skill metadata, and documents repeatable tasks such as releases, changelog work, pull request landing, and subagent coordination.
Why it's ranked here
The project offers unusually concrete operational guidance, especially around safe releases and repeatable agent handoffs. Its strongest ideas are idempotent synchronization, explicit collision handling, and project-local rules layered over shared defaults. The verdict is mixed for broader adoption because many conventions reflect one developer’s machines, repositories, credentials, and release stack.
What's good
The synchronization design avoids overwriting real files, removes stale managed links, and reports duplicate skill names. Skill metadata follows a small required schema, which makes routing easier to check. The documentation also turns fragile work into explicit checklists, including signing, notarization, release asset verification, changelog curation, pull request gates, and credential handling through persistent terminal sessions.
Tradeoffs
Setup assumes fixed home-directory conventions, sibling repositories, symbolic links, and behavior specific to Codex and Claude Code. Mac usage receives the deepest treatment, while Windows requires Bun for supplied shims and may not honor Unix launch headers directly. Several workflows also assume GitHub tooling, terminal multiplexing, Apple release infrastructure, or personal credential arrangements that teams must adapt.
How to use it well
It best suits an engineer maintaining several repositories with Codex or Claude Code who wants one source for agent policy, reusable prompts, and release discipline. Adopt the synchronization and validation conventions, then keep project-specific rules below the shared pointer. Treat the workflow documents as adaptable playbooks. It does not replace each project’s tests, build configuration, credentials, or release metadata.
Technical notes+
README.md describes an idempotent link-based discovery system: Codex receives whole skill-root links, while Claude Code receives a flat per-skill mirror; collisions prefer this repository, then the manager repository, then machine-local skills. It also says managed synchronization prunes stale links without clobbering real files and validation checks YAML front matter for required names and descriptions. package.json declares a private ES module package with Commander and Puppeteer Core dependencies. docs/windows.md says Windows users should invoke Bun-based shims through Bun because direct shebang execution may fail in PowerShell.
Observed
- Packaging
- Private JavaScript ES module package with Commander and Puppeteer Core dependencies.
- Interfaces
- Command-line helpers, reusable prompt commands, agent instruction files, and skill metadata.
- Agent support
- Documents global skill discovery and shared instruction setup for Codex and Claude Code.
- Platform support
- Mac synchronization is the primary setup; Windows notes prescribe Git for Windows and Bun.
- Skill format
- Each skill uses YAML front matter with required name and quoted description fields.
- Release scope
- Includes detailed playbooks for GitHub releases, macOS signing, notarization, Sparkle updates, and npm publishing.
Read from README.md, package.json, docs/mac-app.md, docs/windows.md, docs/subagent.md, docs/RELEASING.md, docs/concurrency.md, docs/RELEASING-MAC.md, docs/slash-commands.md, docs/update-changelog.md, docs/npm-publish-with-1password.md, docs/slash-commands/raise.md, docs/slash-commands/README.md, docs/slash-commands/landpr.md, docs/slash-commands/pickup.md.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.