agentmods.dev

Stop

A pair of commands that runs automatically when the agent finishes a response to check the written specification and the implementation.

In plain words
What is it for?
Use it to run the provided specification and implementation validation scripts after the agent responds.
Why use it?
It can catch specification or implementation problems at the end of an agent task.

Hook

4 4d ago A scan tokens not measured original MIT
View the source file bitcraft-apps/spec-first
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/bitcraft-apps/spec-first/stop
Clone the repo
git clone --depth 1 https://github.com/bitcraft-apps/spec-first
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 yesterday.

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.

hooks/hooks.json · 16 lines

What it actually says

{
  "Stop": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/validate-spec.sh"
        },
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/validate-implementation.sh"
        }
      ]
    }
  ]
}
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.

  1. yesterday First seen · 16 lines scan A 13a3c91b15c7

Subscribe to this mod's changes

Stop is a hook published in the GitHub repository bitcraft-apps/spec-first (4 stars, last pushed 4d 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 GenerationPlanningProductivityai-workflowclaude-codeclaude-code-plugindeveloper-toolsrequirements
Related

Other hooks, from other repositories

PostToolUse

Runs after a tool call finishes for Edit and Write tool calls, running an inline shell check. From KhazP/vibe-coding-prompt-template.

KhazP/vibe-coding-prompt-template · not measured

PostToolUse

Runs after a tool call finishes for Edit and Write tool calls, running bun run lint. From gmickel/flow-next.

gmickel/flow-next · not measured

SessionStart

Runs when a session starts on startup, clear and compact, running an inline shell check. From voidvec/drogon-claude-plugin.

voidvec/drogon-claude-plugin · not measured

Stop

Runs when the agent finishes a response, running an inline shell check. From openplanr/planr-pipeline.

openplanr/planr-pipeline · not measured

PreCompact

Runs before the context is compacted, executing pre-compact.js via node. From atuljha23/holocron.

atuljha23/holocron · not measured

PostToolUseFailure

Runs when a tool call fails, executing agent_state.py via bash. From pillip/claude-dev-kit.

pillip/claude-dev-kit · not measured