hook-development

hook-development is a skill for Claude Code from Sivan757/dsh-agent-plugins-market. It costs 113 tokens per session (3,834 once invoked), scanned A, original, MIT.

A guide to hooks, which are scripts that run when events such as tool use, session start, or task completion occur. It covers command-based hooks for checking actions, processing results, loading context, and enforcing completion rules.

In plain words
What is it for?
Use it to create pre-tool checks, react after tools run, load project context, block unsafe operations, or verify conditions before work ends.
Why use it?
It lets a plugin respond automatically at specific points instead of relying only on the agent to remember an instruction. This can add deterministic checks and workflow steps around tool use.

Skill for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: mentions subagents.

Good fit Use it to create pre-tool checks, react after tools run, load project context, block unsafe operations, or verify conditions before work ends.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sivan757/dsh-agent-plugins-market/hook-development
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.

Any agent
npx skills add Sivan757/dsh-agent-plugins-market --skill hook-development
Clone the repo
git clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-market

Made for: Claude Code.

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

agentmods badge for hook-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/hook-development/github.svg)](https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/hook-development)
Your own site
<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/hook-development"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/hook-development/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.

agentmods 80×15 button for hook-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/hook-development"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/hook-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,834 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00113 $0.03834
Opus 5.5 $0.00045 $0.01534
Sonnet 5.5 $0.00023 $0.00767
Haiku 4.5 $0.00011 $0.00383

Measured today against content hash 631c28dd3932, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hook-development 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 today.

The scan reads SKILL.md. This mod also ships 6 executable files (examples/load-context.sh, examples/validate-bash.sh, examples/validate-write.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/plugin-dev/skills/hook-development/SKILL.md · 676 lines

How it starts

The opening of the file, as written. The whole thing — 676 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hook Development for DeepSeek Harness Plugins

Overview

Hooks are event-driven automation scripts that execute in response to DeepSeek Harness events. Use hooks to validate operations, enforce policies, add context, and integrate external tools into workflows.

Key capabilities:

  • Validate tool calls before execution (PreToolUse)
  • React to tool results (PostToolUse)
  • Enforce completion standards (Stop, SubagentStop)
  • Load project context (SessionStart)
  • Automate workflows across the development lifecycle

Hook Types

Command Hooks (The Supported Type)

Execute bash commands for deterministic checks:

{
  "type": "command",
  "command": "bash ${PLUGIN_ROOT}/scripts/validate.sh",
  "timeout": 60
}

Use for:

  • Fast deterministic validations
  • File system operations
  • External tool integrations
  • Performance-critical checks

Hook Configuration Formats

Plugin hooks.json Format

For plugin hooks in com.deepseek.harness/hooks/hooks.json, use wrapper format:

{
  "description": "Brief explanation of hooks (optional)",
  "hooks": {
    "PreToolUse": [...],
    "Stop": [...],
    "SessionStart": [...]
  }
}

Key points:

  • description field is optional
  • hooks field is required wrapper containing actual hook events
  • This is the plugin-specific format

Example:

{
  "description": "Validation hooks for code quality",
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Write",
        "hooks": [
          {
            "type": "command",
            "command": "${PLUGIN_ROOT}/hooks/validate.sh"
          }
        ]
      }
    ]
  }
}

Settings Format (Direct)

For a standalone hook file (for example a project .agents/hooks/hooks.json), use the bare event-table format:

{
  "PreToolUse": [...],
  "Stop": [...],
  "SessionStart": [...]
}

Key points:

  • No wrapper - events directly at top level
  • No description field
  • This is the settings format

Important: The examples below show the hook event structure that goes inside either format. For plugin hooks.json, wrap these in {"hooks": {...}}.

Read the full file on GitHub · 676 lines

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. today First seen · 676 lines · 113 tokens per session scan A 631c28dd3932

Subscribe to this mod's changes

hook-development is a skill published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 3,834 once invoked, about $0.0005 per session on Opus 5.5. 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-10-18.

Related

Other skills, from other repositories

manage-taskboard

Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…

shengsheng90/DSH-taskboard · 88 tokens

company-research-method

A documented process for researching a company using supplied files and selected public sources. It produces a company overview with business details, sourced financial figures, and stated risks.

PerryLink/dsh-industry-research · 83 tokens

promentor

A tool that turns a software project into a hands-on course in the style of an MIT course. It can produce lessons, code walkthroughs, practical labs, behavior tests, grading, explanations, and AI reviews.

Lyn-77/ProMentor · 85 tokens

dsh-plugin-guide

Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…

PerryLink/dsh-plugin-guide · 76 tokens

delivery-proof

Delivery proof and the doublecheck report. Use when the work is done and the delivery must be proven — consolidate the spec, test timeline, review verdicts, and verification checks into a doublecheckreport, and only then claim completion.

PerryLink/dsh-doublecheck · 50 tokens

playlet-wechat-feed

A daily report of popular short-drama articles from WeChat public accounts, a Chinese publishing platform, grouped by story themes and accompanied by writing insights.

redfox-data/redfox-community-dsh · 269 tokens