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.
/plugin marketplace add ishtartec/claude-code-ghosttynpx agentmods add plugins/ishtartec/claude-code-ghostty/ghostty-notifygit clone --depth 1 https://github.com/ishtartec/claude-code-ghosttyGrade A, and why
ghostty-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 yesterday.
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": "ghostty-notify",
"description": "Native Ghostty desktop notifications for Claude Code (idle input / permission request / turn finished) via OSC 777. Per-tab suppression and click-to-focus are handled natively by Ghostty. Runs only under Ghostty.",
"version": "1.0.0",
"author": {
"name": "ishtartec",
"url": "https://github.com/ishtartec"
},
"homepage": "https://github.com/ishtartec/claude-code-ghostty",
"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.
- yesterday First seen · 12 lines scan A d4d3599a4703
ghostty-notify is a plugin published in the GitHub repository ishtartec/claude-code-ghostty (1 stars, last pushed 2mo 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-08-31.
Other plugins, from other repositories
terminal-agent-visual-signals
Plugin marketplace listing 1 plugin: tavs.
tavs
Visual terminal state indicators for Claude Code sessions using OSC escape sequences. Changes background color and tab title based on Claude's state (processing, permission, idle, complete, compacting, subagent, toolerror).
agent-harness-plugins
Plugin marketplace listing 51 plugins: add-cobra-version, add-community-files, add-goreleaser-homebrew, add-scrut-cli-tests, address-issue.
add-cobra-version
Add a version subcommand with build metadata (version, commit hash, build date, Go runtime version, optional JSON output) to an existing Cobra-based Go CLI, wiring up ldflags in main.go, the cmd package, GoReleaser, and the Makefile.
add-goreleaser-homebrew
Add GoReleaser and Homebrew tap publishing to an existing Go CLI project with conditional support for completions, man pages, and macOS-only builds.
bootstrap-project
Assess a repository, determine what scaffolding and setup tools are needed, present a plan, and execute them in the correct order.