Awesome Mac is a categorized directory of macOS software that helps people discover applications for different needs. Contributors add and organize software recommendations, while users browse the collection to find Mac tools. Its catalogue entry is a skill related to using or maintaining this software list.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jaywcjlove/awesome-mac --skill awesome-mac-maintainergit clone --depth 1 https://github.com/jaywcjlove/awesome-macWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jaywcjlove/awesome-mac/awesome-mac-maintainer)<a href="https://agentmods.dev/skills/jaywcjlove/awesome-mac/awesome-mac-maintainer"><img src="https://agentmods.dev/badge/skills/jaywcjlove/awesome-mac/awesome-mac-maintainer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jaywcjlove/awesome-mac/awesome-mac-maintainer"><img src="https://agentmods.dev/badge/skills/jaywcjlove/awesome-mac/awesome-mac-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.00759 |
| Opus 5.5 | $0.00026 | $0.00304 |
| Sonnet 5.5 | $0.00013 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
awesome-mac-maintainer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Awesome Mac Maintainer
Use this skill for repository curation tasks that touch app listings, especially when the user wants to add, update, or reclassify an app across the English, Chinese, Japanese, and Korean READMEs.
Use this skill for
- Add a new app entry to the right category in
README.md. - Sync the same app into
README-zh.md,README-ja.md, andREADME-ko.md. - Update or shorten an existing listing without drifting from repository style.
- Move an entry to a better category while preserving local document structure.
For supported repository files and scope boundaries, see references/supported-files.md.
Core workflow
- Identify the most appropriate category by searching the existing README files for similar apps or keywords.
- Read the local context around the target section in each language before editing.
- Add or update the entry in all required language files.
- Keep the description to one sentence.
- Verify placement, wording, and formatting with
rgandgit diff.
Curation rules
- Match the local section used by each document instead of assuming all four files have identical structure.
- Preserve existing ordering within a section. In practice this is usually alphabetical by app name.
- Do not rewrite neighboring entries unless needed for the requested task.
- Keep edits narrowly scoped to the requested listing work.
Description style
- Explain what the app is in one sentence.
- Keep it brief and concrete.
- Prefer product identity over feature lists.
- Do not emphasize that the app is a macOS app unless that detail is necessary.
- Avoid marketing phrasing unless the repository already uses it for that exact product.
Preferred patterns:
- "Open-source HTTP(S) debugging proxy for intercepting, inspecting, modifying, and replaying requests."
- "Open-source screen recorder and editor for polished demos, tutorials, and product videos."
- "Open-source tool for switching Git identities and managing SSH keys."
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 76 lines · 64 tokens per session scan A 37e19318edd5
awesome-mac-maintainer is a skill published in the GitHub repository jaywcjlove/awesome-mac (117,343 stars, last pushed today), licensed CC0-1.0. It adds 64 tokens to every session and 759 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ios-signing-troubleshooting
Diagnose iOS code signing, provisioning profile, entitlement and certificate errors from Xcode or xcodebuild. Use when a build, archive or export fails with signing errors, "No profiles found", "Provisioning profile doesn't include", or keychain problems.
ios-simulator-build-run
Build an iOS app and run it on the Simulator, then read build errors, logs and screenshots. Use when asked to build, run, launch, test or debug an iOS/iPadOS app, or when xcodebuild fails.
ios-simulator-ui-automation
Drive a booted iOS Simulator like a user with the axe CLI (describe-ui, tap, swipe, type, screenshot, record-video) to verify UI flows, reproduce bugs and capture screenshots. Use when asked to tap, scroll, type into, screenshot or smoke-test a running iOS app.
ios-testflight-release
Archive an iOS app, upload it to TestFlight and submit it to the App Store using the asc (App Store Connect) CLI, with a pre-release checklist. Use when asked to ship, release, upload a build, distribute a beta, or submit to App Review.
macos-build-test
Build, run and test macOS apps and Swift packages from the command line with XcodeBuildMCP, xcodebuild and swift. Use when asked to build, launch, test or debug a macOS target, a Swift package, or a menu bar, AppKit or SwiftUI Mac app.
macos-notarize-distribute
Sign with Developer ID, notarize with Apple, staple and package a macOS app as a DMG or ZIP for distribution outside the Mac App Store, using codesign and the asc CLI. Use when asked to notarize, staple, or ship a Mac app directly.