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-testgit 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-test)<a href="https://agentmods.dev/skills/ruiiiovo/claude-code-bark-notify/bark-notify-test"><img src="https://agentmods.dev/badge/skills/ruiiiovo/claude-code-bark-notify/bark-notify-test/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-test"><img src="https://agentmods.dev/badge/skills/ruiiiovo/claude-code-bark-notify/bark-notify-test.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.00047 | $0.00429 |
| Opus 5 | $0.00023 | $0.00215 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
bark-notify-test 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 9d 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
Bark Notify Test
Send one verification notification using the user's local Bark script or Bark configuration.
Behavior
- Detect the current OS (same method as setup: check working directory path or
$env:OS). - Check for the platform-specific script:
- macOS/Linux:
~/.claude/claude-stop-bark.sh - Windows:
%USERPROFILE%\.claude\claude-stop-bark.ps1(resolve the absolute path)
- macOS/Linux:
- If the script exists, use it for the test instead of inventing a second send path.
- Pipe a
Stoppayload with the current or user-provided project name through the script:- macOS/Linux:
echo '{"hook_event_name":"Stop","cwd":"/path/to/project"}' | bash ~/.claude/claude-stop-bark.sh - Windows:
echo '{"hook_event_name":"Stop","cwd":"C:\\path\\to\\project"}' | powershell.exe -ExecutionPolicy Bypass -NoProfile -NonInteractive -File "C:\Users\<username>\.claude\claude-stop-bark.ps1"
- macOS/Linux:
- Tell the user exactly what should appear on the phone:
- title = project name
- body =
✅ Claude Code 已完成
- If the notification fails, read
../bark-notify/references/troubleshooting.mdand debug from there.
Notes
- Prefer a real push test over a dry run when the user explicitly asks for verification.
- For encrypted mode, the most common failure is mismatched Bark iPhone settings or wrong key.
- On Windows, if powershell.exe exits with a non-zero code, check that the absolute script path is correct and that the script file exists.
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.
- 9d ago First seen · 31 lines · 47 tokens per session scan A 208527a94b6b
bark-notify-test is a skill published in the GitHub repository RUIIIOVO/claude-code-bark-notify (5 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 429 once invoked, about $0.0002 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-31.
Other skills, from other repositories
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
vibeguard-setup
Use when the user asks to install, verify, inspect, or remove VibeGuard Codex hooks through the Codex App plugin.
review-pr
Perform a comprehensive code review of a pull request.
guide-recap
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate release notes, announcements, social media posts, or recap summaries from guide updates.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.