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 agentmods add skills/artemnovichkov/skills/xcodebuild-notifynpx skills add artemnovichkov/skills --skill xcodebuild-notifygit clone --depth 1 https://github.com/artemnovichkov/skillsWrote 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/artemnovichkov/skills/xcodebuild-notify)<a href="https://agentmods.dev/skills/artemnovichkov/skills/xcodebuild-notify"><img src="https://agentmods.dev/badge/skills/artemnovichkov/skills/xcodebuild-notify.svg" alt="Measured on agentmods" height="20"></a>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.00052 | $0.00419 |
| Opus 5 | $0.00026 | $0.00210 |
| Sonnet 5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
xcodebuild-notify 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 5d 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.
What it actually says
xcodebuild-notify
macOS notifications for xcodebuild commands, mimicking Xcode's native build notifications.
When to Use
This skill activates automatically via a PostToolUse hook on Bash commands. No manual invocation needed — any xcodebuild command triggers it.
How It Works
The hook script (hooks/scripts/xcodebuild-notify.sh) runs after every Bash tool use:
- Checks if the command contains
xcodebuild— exits early if not - Parses
-schemeand-projectflags from the command - Checks tool output for
BUILD SUCCEEDEDorBUILD FAILED - Sends a macOS notification via
osascript
Hook Configuration
The PostToolUse hook is defined in hooks/hooks.json:
{
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "bash $CLAUDE_PLUGIN_ROOT/hooks/scripts/xcodebuild-notify.sh",
"async": true
}
]
}
]
}
Notification Examples
Build succeeds:
Title: "Build Succeeded"
Body: "MyScheme | MyApp Project"
Build fails:
Title: "Build Failed"
Body: "MyScheme | MyApp Project"
Commands that don't produce BUILD SUCCEEDED or BUILD FAILED (e.g., xcodebuild clean, xcodebuild -help) are silently skipped.
Requirements
- macOS (uses
osascriptfor notifications) jq(brew install jq) — parses hook input JSON
What ships with it
5 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.
- 5d ago First seen · 64 lines · 52 tokens per session scan A c02b08e9b35b
xcodebuild-notify is a skill published in the GitHub repository artemnovichkov/skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 419 once invoked, about $0.0003 per session on Opus 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
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
dev-environment-bootstrapping
Use this skill when the user asks to bootstrap, set up, create, or initialize a Shopware development environment from scratch — phrases like "set up a Shopware dev environment", "clone and install Shopware", "initialize a Shopware plugin project", "bootstrap Shopware and a new plugin called X", "get a fresh Shopware…
structuring-documentation
Use when writing, editing, auditing, splitting, or measuring Markdown documentation surfaces — README.md, AGENTS.md, CLAUDE.md, and docs/ siblings. Triggers include "is this doc too long", "split this README", "measure the docs", "where does this documentation belong", "audit the documentation", and any request to…
phpunit-integration-test-generation
Use this skill when the user asks to generate, write, or create integration tests for a Shopware 6 source class whose contract requires wired-up code — phrases like "generate integration tests for X", "write an integration test for this controller", "test this indexer", "create an integration test for the message…
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…