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.
npx skills add Sivan757/dsh-agent-plugins-market --skill hook-developmentgit clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-marketWrote 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/skills/sivan757/dsh-agent-plugins-market/hook-development)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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.
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:
descriptionfield is optionalhooksfield 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": {...}}.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/load-context.sh 1.6 KB runs code
- examples/validate-bash.sh 1.3 KB runs code
- examples/validate-write.sh 1.2 KB runs code
- references/advanced.md 9.7 KB
- references/migration.md 7.5 KB
- references/patterns.md 6.1 KB
- scripts/hook-linter.sh 4.1 KB runs code
- scripts/README.md 3.6 KB
- scripts/test-hook.sh 5.2 KB runs code
- scripts/validate-hook-schema.sh 4.2 KB runs code
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.
- today First seen · 676 lines · 113 tokens per session scan A 631c28dd3932
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.
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…
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.
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.
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…
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.
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.