startup
Skill1 starsChanged 17 days agoMITView on GitHub
Explain what starts with this Mac (login items, launch agents and daemons, background items) and what's worth a look. Use when the human asks what runs at startup or login on their Mac, why the Mac is slow to start, about background items, or whether something on their Mac is suspicious. Not for a project's or app's own startup code.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- jdonohoo/vern-bottheir own version, first seen Nov 15, 2026
- withpiper/pipekittheir own version, first seen Nov 8, 2026
- MatthewMair42/claude-configtheir own version, first seen Oct 12, 2026
- open-guji/luatex-cntheir own version, first seen Oct 9, 2026
- chadthornton/claude-continuitytheir own version, first seen Sep 30, 2026
- issue-orchestrator/issue-orchestratortheir own version, first seen Sep 6, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- sonichi/sutando★ 396same name
- open-guji/luatex-cn★ 127same name
- mr-daedalium/ostack-saas★ 108same name
- mathruffian-dot/cross-device-agent-skills★ 27same name
- jdonohoo/vern-bot★ 15same name
- issue-orchestrator/issue-orchestrator★ 10same name
- withpiper/pipekit★ 6same name
- iXanadu/tiding★ 3same name
- joyozhang333-lgtm/sage-coach★ 3same name
- inbornerrorofmetabolismdisraeli330/sage-coach★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Never call something malware without evidence.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Works from any folder on this Mac (0009). Run syscalls as
cos …; in the Ovenbird folder,bin/cos …is the same. Whatever youcos rememberorcos friction addis about the human or this Mac, never the project or client you're working in.
Startup
Steps
cos startup --json. It's read-only and needs no permission: the launch agents and daemons (the launchd plists, with their on/off state), plus who signed each program. It doesn't list apps that open at login. If the human wants those too, tell them first that macOS will show an admin password dialog, then runcos startup --full --json(it asks for an Allow). Never run--fullon your own or in a headless run.- Lead with the answer: how many things start, and whether anything needs attention.
- Items worth a look come first (
findings). For each one, say in plain language what it probably is (use the name, developer and path; you know most common apps and tools), why it was flagged, and what you'd do:- program missing: left behind by something that was removed; safe to remove the item.
- unsigned / ad hoc: often a developer tool or something the human built (Homebrew builds are ad-hoc signed); only worrying if they don't recognize it.
- runs a script: scripts can't be signed; read what it runs (the path) and say so.
- on but unused for months: a candidate to turn off.
- Then a short summary of the rest, grouped (apps, launch agents, daemons). No wall of items.
- Changing things: point to System Settings › General › Login Items & Extensions. Removing
a user launch agent (
launchctl bootout gui/$UID/<label>plus deleting its plist in ~/Library/LaunchAgents) changes the Mac: explain exactly what you'd run and only do it when the human says yes. Never touch /Library/LaunchDaemons (needs admin).
Rules
- Never call something malware without evidence; say what you know and what you don't.
- Item names stay in this conversation: don't write them into the repo or friction.
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
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.

