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/michalstrnadel/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/plugins/michalstrnadel/scorekeeper/claude-code-plugin)<a href="https://agentmods.dev/plugins/michalstrnadel/scorekeeper/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/michalstrnadel/scorekeeper/claude-code-plugin/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/plugins/michalstrnadel/scorekeeper/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/michalstrnadel/scorekeeper/claude-code-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scorekeeper 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 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": "scorekeeper",
"description": "Commitment tracking for LLM agents — a deontic scoreboard of what the agent is entitled to claim and to do; catches drift and overreach.",
"version": "0.4.0",
"author": {
"name": "Michal Strnadel",
"url": "https://github.com/michalstrnadel/scorekeeper"
},
"homepage": "https://github.com/michalstrnadel/scorekeeper",
"repository": "https://github.com/michalstrnadel/scorekeeper",
"license": "Apache-2.0",
"keywords": ["commitment-tracking", "agent-memory", "context-engineering", "inferentialism", "scope-control", "overreach"]
}
What it installs
The manifest is a name and a version. 6 hooks travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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 · 14 lines scan A 01c8b1b9901a
scorekeeper is a plugin published in the GitHub repository michalstrnadel/scorekeeper (3 stars, last pushed 2mo ago), licensed Apache-2.0. 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
aria-knowledge
ARIA — Applied Reasoning and Insight Architecture. Persistent human-governed knowledge for Claude Code via a five-phase lifecycle: capture → govern → promote → apply → refresh. Stages session insights/decisions/feedback into review backlogs, promotes approved items to a tag-indexed markdown base, and applies them via…
aria-cowork
Knowledge management for Claude Cowork — capture, organize, and apply durable knowledge across your work, available in any project workspace via a persistent folder grant. Companion to aria-knowledge for Claude Code; both share one knowledge folder so insights flow between conversational and engineering work. Default…
aria-probe
Validation probe for aria-cowork. Tests whether a Cowork plugin can read and write the user-attached knowledge folder, verifies bidirectional access with aria-knowledge in Code, and (v0.2.0) tests whether Cowork can read the existing aria-knowledge config at /.claude/aria-knowledge.local.md when /.claude/ is attached.
titen-memory
Use Titen's evidence-grounded collaborative memory. The local stdio mode needs no configuration; a served Titen endpoint is the alternative for a shared store.
halomem
HaloMem organizational memory: session-start recall, session-end capture, MCP tools. Configure with HALOMEMURL and HALOMEMAPIKEY.
cwc-makers
Seamless onboarding for the Code-with-Claude Makers Cardputer: one /maker-setup command clones the build-with-claude repo, flashes UIFlow firmware, and installs the Claude Buddy app bundle onto a freshly-plugged-in M5Stack Cardputer-Adv.