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 Sassy-Dog/sassydog-skills/plugin install sassy-dogWrote 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/sassy-dog/sassydog-skills/setup-hooks)<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/setup-hooks"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/setup-hooks/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/sassy-dog/sassydog-skills/setup-hooks"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/setup-hooks.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.00167 | $0.03377 |
| Opus 5 | $0.00084 | $0.01688 |
| Sonnet 5 | $0.00033 | $0.00675 |
| Haiku 4.5 | $0.00017 | $0.00338 |
Grade B, and why
setup-hooks scanned grade B with 1 finding 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 12d ago.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`grep -o 'markdownlint-cli2[^"]*' .claude/hooks/sassydog-post-edit.sh` against the probe's How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Hooks
Generator for per-repo Claude Code hooks: inspect the repo's actual stack, render a
formatter/linter dispatcher tailored to it, wire it into .claude/settings.json, and reconcile all
of it on every re-run. The sibling of setup-config — same philosophy: the plugin ships
the generator, the repo owns a generated, refreshable artifact.
Why hooks and not instructions: formatting/lint feedback belongs at the harness layer, firing on every Edit/Write deterministically — not re-taught per session. A repo-specific render beats a global hook because a global one fires uselessly in repos whose stack it doesn't match.
What gets generated
.claude/hooks/sassydog-post-edit.sh— a PostToolUse (Edit|Write) dispatcher rendered fromreferences/templates/sassydog-post-edit.template.sh. It reads the hook event JSON on stdin, extracts the edited file path, and routes by extension to the tools the repo actually has. Contract: formatters fix silently (exit 0); linters with unfixable findings exit 2 so the harness feeds the findings straight back for an immediate fix — defects surface at edit time, not in the PR review loop..claude/hooks/sassydog-artifact-guard.sh— a stray-artifact guard rendered fromreferences/templates/sassydog-artifact-guard.template.sh. Stack-agnostic, so it is always generated and has no conditional blocks. It keeps screenshots and other throwaway binaries out of the repo root, where they accumulate unnoticed — invisible togit diff, breaking nothing, and indistinguishable later from a deliberate asset. The sanctioned destination istmp/, whichsassy-dog:repo-cleanupalready auto-discards universally, sotidy-reposweeps it with no per-repo config. Contract: it reports, it never moves or deletes.- The settings entries in
.claude/settings.json(orsettings.local.jsonwhen the user wants personal-only): onehooks.PostToolUseentry per script, plus onehooks.Stopentry for the guard's catch-all scan. Seereferences/settings-merge.md. - A root-anchored
/tmp/line in the target repo's.gitignore— the destination the guard points at. Owned here rather than bysetup-configbecause a guard whose destination is not ignored just relocates the mess; the two must not drift apart.
What ships with it
5 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.
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.
- 12d ago First seen · 218 lines · 167 tokens per session scan B be41d1e15fe6
setup-hooks is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 167 tokens to every session and 3,377 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.