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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/plugins/athola/claude-night-market/herald)<a href="https://agentmods.dev/plugins/athola/claude-night-market/herald"><img src="https://agentmods.dev/badge/plugins/athola/claude-night-market/herald.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
herald 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
{
"name": "herald",
"version": "1.9.19",
"description": "Standalone notification system for Claude Code plugins. Provides GitHub issue alerts and webhook support (Slack, Discord, generic).",
"skills": [],
"commands": [],
"agents": [],
"hooks": [],
"keywords": [
"notifications",
"alerts",
"webhooks",
"github-issues",
"slack",
"discord"
],
"author": {
"name": "Alex Thola",
"url": "https://github.com/athola"
},
"license": "MIT"
}
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 · 23 lines scan A 525a1b7d9fdf
herald is a plugin published in the GitHub repository athola/claude-night-market (336 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
claude-bionify
Bionic reading for Claude's responses that bolds the leading part of each word to guide your eyes and enable you to read faster.
claude-session-tint
Know which Claude Code session needs you. Tints a Terminal.app window by project and brightens it when a response lands unseen.
studio-coach
PROACTIVELY use this agent when complex multi-agent tasks begin, when agents seem stuck or overwhelmed, or when the team needs motivation and coordination. This agent serves as the elite performance coach for all other agents, ensuring they operate at their highest level while maintaining composure and excellence.…
lark
A plugin for operating Feishu/Lark workplace services such as messages, documents, spreadsheets, calendars, files, tasks, and meetings through a local command-line tool.
chat-saver
Save, search, manage, and export Claude Code conversations to documents or external platforms.
vault-template
Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching.