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 michalstrnadel/scorekeeper/plugin install scorekeeperWrote 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/michalstrnadel/scorekeeper/session-start)<a href="https://agentmods.dev/hooks/michalstrnadel/scorekeeper/session-start"><img src="https://agentmods.dev/badge/hooks/michalstrnadel/scorekeeper/session-start/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/hooks/michalstrnadel/scorekeeper/session-start"><img src="https://agentmods.dev/badge/hooks/michalstrnadel/scorekeeper/session-start.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
This is a copy
95% identical to SessionStart — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run.sh\" session-start",
"timeout": 15
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 13 lines scan A 947c901a6ab1
SessionStart is a hook published in the GitHub repository michalstrnadel/scorekeeper (3 stars, last pushed 2mo ago), licensed Apache-2.0. 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. It is 95% identical to SessionStart, differing in 3 lines, and is treated as a copy.
Other hooks, from other repositories
PreCompact
Runs before the context is compacted, executing on_pre_compact.sh. From atomicstrata/atomicmemory.
PostCompact
Runs after the context is compacted, executing on_post_compact.sh. From atomicstrata/atomicmemory.
PreToolUse
Runs before the agent uses a tool for Write and Edit tool calls, executing block_memory_write.sh. From atomicstrata/atomicmemory.
TaskCompleted
Runs when a task is marked completed, executing on_task_completed.sh. From atomicstrata/atomicmemory.
PostToolUse
Runs after a tool call finishes for Write, Edit and MultiEdit tool calls, executing post-format.sh. From lx-wnk/Agent-Context.
SubagentStop
Runs when a subagent finishes, executing subagent-scope.sh. From lx-wnk/Agent-Context.