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 kirollosatef/customgpt-claude-quadruple-verification/plugin install customgpt-claude-quadruple-verificationWrote 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/kirollosatef/customgpt-claude-quadruple-verification/stop)<a href="https://agentmods.dev/hooks/kirollosatef/customgpt-claude-quadruple-verification/stop"><img src="https://agentmods.dev/badge/hooks/kirollosatef/customgpt-claude-quadruple-verification/stop/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/kirollosatef/customgpt-claude-quadruple-verification/stop"><img src="https://agentmods.dev/badge/hooks/kirollosatef/customgpt-claude-quadruple-verification/stop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 18 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/stop-gate.mjs\"",
"timeout": 15000
},
{
"type": "prompt",
"prompt": "When your response includes code changes, file modifications, or research content, perform the following verification before finishing. Skip entirely when returning structured data (JSON, API responses) or answering simple conversational questions.\n\n=== CODE QUALITY REVIEW ===\nReview all code you wrote or modified:\n- Any incomplete implementations, stubs, or placeholder logic?\n- Functions that log/print but don't implement real logic?\n- Missing error handling for failure cases?\n- Edge cases not handled (empty inputs, null values, boundaries)?\n- Does the code match what was requested, or were parts skipped?\nIf issues found: fix them before presenting.\n\n=== SECURITY REVIEW ===\nReview all code and commands for security risks:\n- Hardcoded credentials, API keys, tokens, or passwords?\n- Injection vulnerabilities (SQL, command, XSS, template injection)?\n- Unsafe deserialization (pickle, yaml.load, eval)?\n- Insecure cryptography (MD5/SHA1 for security, JWT none algorithm)?\n- Path traversal, SSRF, or prototype pollution risks?\n- Overly permissive permissions, CORS, or file access?\nConsider context: test files and examples have different risk profiles than production code.\nIf issues found: fix them before presenting.\n\n=== RESEARCH CLAIMS ===\nIf you wrote documentation or research content (.md files):\n- Are statistical claims (percentages, dollar amounts, growth rates) sourced with URLs?\n- Are factual assertions specific (named study, author, year) rather than vague?\n- If you have search tools available (Perplexity MCP, WebSearch, or WebFetch), verify key claims now.\n- After verifying, add <!-- VERIFIED --> to the file.\n- If no search tools are available, flag unverifiable claims cleWhat else hooks.json configures
This page is one entry in a file that holds 3. 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.
- 8d ago First seen · 18 lines scan A 29e4760f243a
Stop is a hook published in the GitHub repository kirollosatef/customgpt-claude-quadruple-verification (16 stars, last pushed 5mo 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-30.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Write, Edit, MultiEdit and TodoWrite tool calls, running npx tdd-guard@latest. From nizos/tdd-guard.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running npx tdd-guard@latest. From nizos/tdd-guard.
SessionStart
Runs when a session starts on startup, resume and clear, running npx tdd-guard@latest. From nizos/tdd-guard.
SessionStart
Runs when a session starts, executing cli.js via node. From code-yeongyu/codex-rules.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.