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 RUIIIOVO/claude-code-bark-notify --skill bark-notify-setupgit clone --depth 1 https://github.com/RUIIIOVO/claude-code-bark-notifyWrote 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/ruiiiovo/claude-code-bark-notify/bark-notify-setup)<a href="https://agentmods.dev/skills/ruiiiovo/claude-code-bark-notify/bark-notify-setup"><img src="https://agentmods.dev/badge/skills/ruiiiovo/claude-code-bark-notify/bark-notify-setup/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/ruiiiovo/claude-code-bark-notify/bark-notify-setup"><img src="https://agentmods.dev/badge/skills/ruiiiovo/claude-code-bark-notify/bark-notify-setup.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.00962 |
| Opus 5.5 | $0.00023 | $0.00385 |
| Sonnet 5.5 | $0.00012 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade B, and why
bark-notify-setup scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: Set up Bark completion notifications for Claude Code on macOS by safely writing the local Bark sender script and merging a Stop hook into ~/.claude/settings.json. Use when the user explicitly asks to configu How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bark Notify Setup
Configure the current macOS Claude Code environment to send a Bark notification when Claude finishes a turn.
Goals
After setup, the local machine should contain:
~/.claude/claude-stop-bark.sh- hooks in
~/.claude/settings.jsonforStop,StopFailure,SessionEnd, andNotificationthat all run that script asynchronously
Required behavior
-
Confirm Bark prerequisites first.
- Read
../bark-notify/references/bark-prereqs.md. - Make sure the user has a Bark push URL.
- Ask whether they want plain mode or encrypted mode.
- If encrypted mode, require a 16-character key and remind them to match Bark app settings on iPhone.
- Read
-
Inspect current Claude config before writing.
- Read
~/.claude/settings.jsonif it exists. - Never overwrite unrelated settings.
- Merge in the
Stop,StopFailure,SessionEnd, andNotificationhooks safely.
- Read
-
Use the config templates from
../bark-notify/references/config-patterns.md.- Write a small shell script to
~/.claude/claude-stop-bark.sh. - Parse
hook_event_name,reason, andcwdfrom the stdin JSON payload usingpython3 -c "..."(do NOT use a python heredoc — it collides with the piped stdin payload). Do NOT read$HOOK_EVENT— Claude Code does not set that env var. - Branch the notification per the event-types table in
config-patterns.md:Stop→✅ Claude Code 已完成, levelactiveNotification→🔔 Claude Code 等待操作, leveltimeSensitive. Filter: parsenotification_typefrom the payload; only send forpermission_promptandelicitation_dialog. Foridle_prompt,auth_success,elicitation_complete,elicitation_response→exit 0silently. Ifnotification_typeis missing (older payload schema), fall back to checkingmessage: skip when it contains"waiting for your input"or"idle", otherwise send.StopFailure→❌ Claude Code 出错, leveltimeSensitiveSessionEndwithreason ∈ {clear, logout, prompt_input_exit}→exit 0immediately, no notification, no bell (this is the user closing the CLI)SessionEndwith any other reason →⚠️ Claude Code 会话异常结束, leveltimeSensitive
- Do NOT set the
soundfield (audio cues opted out). Body emoji +levelalready differentiate events. - title = project name (basename of
cwd); do NOT set theiconfield (Cloudflare gates the official Claude icon; let Bark use its default). - End the script with
printf '\a'(terminal bell) for tmux/terminal notifications. The user-initiatedSessionEndbranch must exit before reaching the bell too.
- Write a small shell script to
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.
- 1mo ago Changed · -30 lines 97a396c9df19
- 1mo ago First seen · 90 lines · 58 tokens per session scan B ebe8551e5f96
bark-notify-setup is a skill published in the GitHub repository RUIIIOVO/claude-code-bark-notify (4 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 962 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
repo-context
Load a compact snapshot of the current repository into context — structure, stack, docs, git state.
publish
Publish the current repository to GitHub, or review and update its GitHub setup.
commit
A tool for creating Git commits in the Conventional Commits format, a shared way to describe changes consistently. It checks the current branch and changes before committing.
push-and-pr
A Git workflow for pushing the current branch and opening a GitHub pull request, which is a request to review and merge code. It follows a rebase-based workflow and prepares a structured pull request.
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…
novu-manage-preferences
Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel…