A pair of checks that run when the coding agent finishes: one runs the project's lint and build commands, and the other notices changes to rule or scoring files.

Use it to validate a project after agent work and flag changes that may require updates to a rule-reference wiki or architecture decision record.

It catches lint or build failures before the response ends and reminds developers to update related documentation when certain files change.

Stop — Hook by let-sunny

Install

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.

agentmods

npx agentmods add hooks/let-sunny/canicode/stop

Clone the repo

git clone --depth 1 https://github.com/let-sunny/canicode

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

Stop 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 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.

.claude/settings.json · 17 lines

What it actually says

{
  "Stop": [
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "[ \"$DEVELOP_SUBAGENT\" = \"1\" ] && exit 0; eval \"$(fnm env 2>/dev/null)\"; OUT=$({ pnpm lint && pnpm build; } 2>&1); [ $? -eq 0 ] || { echo '[stop-hook] pnpm lint/build FAILED' >&2; echo \"$OUT\" >&2; exit 1; }"
        },
        {
          "type": "command",
          "command": "[ \"$DEVELOP_SUBAGENT\" = \"1\" ] && exit 0; CHANGES=$({ git diff --name-only HEAD~1 HEAD; git diff --name-only; git diff --cached --name-only; } 2>/dev/null | sort -u); if echo \"$CHANGES\" | grep -qE '^src/core/(rules/|engine/scoring)'; then printf '%s\\n' '{\"systemMessage\": \"[rule-docs reminder] Rule/scoring files changed. Rule-Reference wiki auto-syncs via sync-rule-docs PostToolUse hook. Check Scoring-Model wiki page (manual) and ADR if scoring philosophy changed.\"}'; fi; exit 0"
        }
      ]
    }
  ]
}

Changes

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 · 17 lines scan A ed39eb99d0fe

Subscribe to this mod's changes

Stop is a hook published in the GitHub repository let-sunny/canicode (10 stars, last pushed 1mo 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-31.

Code review Planning claude-code cursor figma figma-mcp figma-to-code mcp

Stop

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

PostToolUse

Stop

SessionStart

Stop

SubagentStop

SessionStart