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 TimJJTing/Claudesaynpx agentmods add plugins/timjjting/claudesay/claudesaygit clone --depth 1 https://github.com/TimJJTing/ClaudesayGrade A, and why
claudesay 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 2d 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": "claudesay",
"version": "2.2.2",
"description": "Renders Claude replies as ASCII character speech bubbles",
"author": {
"name": "TimJJTing"
},
"license": "MIT",
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/session-start.sh"
}
]
}
],
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/prompt-submit.sh"
}
]
}
],
"PreToolUse": [
{
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/pre-tool-use.sh"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/stop.sh"
}
]
}
]
}
}What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 88 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 2d ago First seen · 51 lines scan A 1f9175699189
claudesay is a plugin published in the GitHub repository TimJJTing/Claudesay (2 stars, last pushed 4mo 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
marketing
Marketing, CRO, SEO and growth skills for Spatie product sites.
guard-hooks
Eight defensive hooks: blocks recursive rm on $HOME, download-and-execute pipelines, secrets-file access, path-less formatter runs, credentials in the staged diff, and the two zsh quoting mistakes that fail silently; warns on stale lockfiles and shellcheck findings; masks credential-shaped values out of Bash output…
context-handoff
Carry work across sessions and keep the context that carries it lean: hand off a session, export or log what it found, chart an effort too big for one sitting, and audit or garbage-collect your Claude Code config.
repo-gate
What runs between "the code works" and "it is pushed": trunk setup, conventional-commit splitting, dependency vulnerability triage, spell-check triage, and babysitting CI until it is green.
cast
Cast integration for Claude Code: emits Coven agent events for local-first session status, notifications, and future UI surfaces.
petsonality
MBTI-based terminal pet companion for Claude Code — MCP server with ASCII art, personality, and reactions.