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 longevityboris/commitmaxxing-hooknpx agentmods add plugins/longevityboris/commitmaxxing-hook/commitmaxxing-hookgit clone --depth 1 https://github.com/longevityboris/commitmaxxing-hookGrade A, and why
commitmaxxing 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": "commitmaxxing",
"description": "Nudges Claude Code to commit granularly after every turn. Keeps your GitHub contribution graph green without breaking rebases or trapping Claude in stop-loops.",
"version": "1.0.0",
"author": {
"name": "Boris Djordjevic",
"url": "https://github.com/longevityboris"
},
"homepage": "https://github.com/longevityboris/commitmaxxing-hook",
"repository": "https://github.com/longevityboris/commitmaxxing-hook",
"license": "MIT",
"keywords": [
"git",
"commit",
"stop-hook",
"automation",
"github-contributions",
"productivity"
]
}
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 · 21 lines scan A 83a7827fd6a1
commitmaxxing is a plugin published in the GitHub repository longevityboris/commitmaxxing-hook (3 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
chonk
Tells you when your Claude Code session has gotten too big, and offers a handoff to a fresh one.
chonk
chonk — a Claude Code plugin that notices when your session has gotten too big.
anlor1002-plugins
Plugin marketplace listing 1 plugin: regressionledger.
regressionledger
Stop your coding agent from re-applying fixes that already failed. Blocks repeat failed fixes across sessions, with the reason attached.
openspec-tools
Plugin marketplace listing 1 plugin: openspec-auto-archive.
openspec-auto-archive
Before every git commit, archives completed OpenSpec changes (all tasks [x]); if openspec archive fails, blocks the commit and asks Claude to invoke opsx:archive, then retry the commit.