Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TeXmeijin/claude-code-mascot-statusline/plugin install claude-code-mascot-statuslineWrote 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/hooks/texmeijin/claude-code-mascot-statusline/session-start)<a href="https://agentmods.dev/hooks/texmeijin/claude-code-mascot-statusline/session-start"><img src="https://agentmods.dev/badge/hooks/texmeijin/claude-code-mascot-statusline/session-start.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
SessionStart 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 6d ago.
A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- PostToolUseFailure — 94% identical, 2 lines differ
- SubagentStop — 92% identical, 2 lines differ
- PermissionRequest — 92% identical, 2 lines differ
- UserPromptSubmit — 92% identical, 2 lines differ
- Notification — 91% identical, 2 lines differ
- SubagentStart — 89% identical, 2 lines differ
- PostToolUse — 89% identical, 2 lines differ
- SessionEnd — 88% identical, 2 lines differ
What it actually says
{
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/cli/hook-state-writer.js\""
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 11. Installing the file brings all of them; each is measured and scanned on its own page.
- Hook Notification A not measured
- Hook PermissionRequest A not measured
- Hook PostToolUse A not measured
- Hook PostToolUseFailure A not measured
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook Stop A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop A not measured
- Hook UserPromptSubmit A not measured
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.
- 6d ago First seen · 12 lines scan A fd6d39373d49
SessionStart is a hook published in the GitHub repository TeXmeijin/claude-code-mascot-statusline (24 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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-30.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup and resume, executing load-context.sh. From YuriNachos/claude-scope.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing add-context.sh. From YuriNachos/claude-scope.
SessionStart
Runs when a session starts, executing session-start.sh via bash. From KKenny0/buddybar.
PostToolUse
Runs after a tool call finishes, executing post-tool-use.sh via bash. From KKenny0/buddybar.
Stop
Runs when the agent finishes a response, executing stop.sh via bash. From KKenny0/buddybar.
SessionStart
Runs when a session starts, executing hook.sh via bash. From 6m1w/claude-sound-fx.