agentleFS
nikshipsnikships/skills-registry/.github/AGENTS.md

skills-registry

AGENTS.md25 starsChanged 6 months agoApache-2.0View on GitHub

Native macOS jobs use the repo-specific runner labeled mac-mini: - ci.yml routes the Swift build/test job to [self-hosted, mac-mini]. Fork pull requests stay on GitHub-hosted infrastructure; only same-repository pull requests and trusted pushes can use the Mini. - release-macapp.yml routes the signed, notarized macOS app release to [self-hosted, mac-mini]. - release.yml routes only the Darwin CLI matrix entries to the Mini. Linux and Windows artifacts remain on GitHub-hosted runners. The Mini runner runs in the logged-in Aqua session. Its job…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the isolated-keychain setup is unavailable and signing must use the login keychain, unlock it once from an interactive Terminal in the …

    line 39
  2. Very specific:

    Check registration from a machine with gh:

    line 65
  3. Very specific:

    Never retarget, stop, remove, or reconfigure another repository's runner, LaunchAgent, work directory, or registration.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

GitHub Actions operations

Self-hosted macOS runner

Native macOS jobs use the repo-specific runner labeled mac-mini:

  • ci.yml routes the Swift build/test job to [self-hosted, mac-mini]. Fork pull requests stay on GitHub-hosted infrastructure; only same-repository pull requests and trusted pushes can use the Mini.
  • release-macapp.yml routes the signed, notarized macOS app release to [self-hosted, mac-mini].
  • release.yml routes only the Darwin CLI matrix entries to the Mini. Linux and Windows artifacts remain on GitHub-hosted runners.

The Mini runner runs in the logged-in Aqua session. Its job environment uses:

JAVA_HOME=/opt/homebrew/opt/openjdk@21
ANDROID_HOME=/Users/nikhilanand/Library/Android/sdk
ANDROID_SDK_ROOT=/Users/nikhilanand/Library/Android/sdk
DEVELOPER_DIR=/Volumes/NVMe/Xcode.app/Contents/Developer

The external NVMe volume must be mounted. Each Xcode job also checks the DEVELOPER_DIR path before building. There is one Mini runner, so native jobs queue rather than running concurrently.

Signing

The Mini's logged-in login keychain contains the Developer ID Application identity, but the release workflows use an isolated temporary keychain loaded from APPLE_DEVELOPER_CERTIFICATE_P12_BASE64 and APPLE_DEVELOPER_CERTIFICATE_PASSWORD. This avoids relying on interactive login-keychain access and avoids duplicate-identity ambiguity by passing the temporary keychain explicitly to every codesign invocation. The release workflows restore the login keychain search list afterward. Notarization still uses APPLE_ID, APPLE_TEAM_ID, and APPLE_APP_SPECIFIC_PASSWORD.

If the isolated-keychain setup is unavailable and signing must use the login keychain, unlock it once from an interactive Terminal in the Mini's logged-in GUI session, then grant the signing tools access:

security unlock-keychain "$HOME/Library/Keychains/login.keychain-db"
security set-key-partition-list -S apple-tool:,apple:,codesign: -s \
  "$HOME/Library/Keychains/login.keychain-db"

Enter the password only at the interactive prompt. Never place it in a workflow, command argument, environment variable, or log. Do not guess an empty password. Do not add a P12 to the normal login-keychain search list.

Operations

The runner is installed separately from runners for other repositories:

ssh nikhilanand@192.168.1.11
cd ~/actions-runner-nikships-skills-registry
./svc.sh status
./svc.sh stop
./svc.sh start

Check registration from a machine with gh:

gh api repos/nikships/skills-registry/actions/runners

Never retarget, stop, remove, or reconfigure another repository's runner, LaunchAgent, work directory, or registration. In particular, leave ~/actions-runner and the ghostty-vibe-xr LaunchAgent untouched.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.