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 agentmods add commands/srstomp/pokayokay/hooksgit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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 | $0.00005 | $0.01580 |
| Opus 5 | $0.00003 | $0.00790 |
| Sonnet 5 | $0.00001 | $0.00316 |
| Haiku 4.5 | $0.00001 | $0.00158 |
Grade A, and why
hooks 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 2d 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.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Management
View the yokay hook system. Hooks are registered via the plugin's
hooks/hooks.json and routed by hooks/actions/bridge.py — all routing and
action lists are code-controlled in bridge.py, not user configuration.
Action: $ARGUMENTS (default: list)
Actions
list (default)
Show all hooks and the actions they run, based on the actual bridge.py routing:
## Active Hooks
| Hook | Trigger | Actions |
|------|---------|---------|
| pre-session | Session start | verify-clean, pre-flight (unattended), recover (if crashed) |
| pre-task | Task moved to in_progress | check-blockers, suggest-skills, setup-worktree |
| post-task | Task marked done | sync, commit, detect-spike, capture-knowledge |
| post-story | All tasks in story done | test, story-integration, audit-gate |
| post-epic | All stories in epic done | audit-gate |
| on-blocker | Blocker set on task | notification |
| pre-commit | Before git commit/add | lint (advisory), check-ref-sizes (blocking) |
| post-command | Audit skill completes | verify-tasks |
| post-review | Reviewer reports FAIL | failure tracking, graduate-rules, post-review-fail (if present) |
| post-session | Session ends | sync, session-summary, curate-memory, session-chain |
| file-change | Edit/Write tool use | WIP tracking (files modified) |
| bash-complete | Bash tool use | WIP tracking (tests, commits, errors) |
history
Show recent hook executions. There is no persistent hook log file — hook
results are emitted inline as additional context after each triggering tool
call. To review recent executions, scan the current session transcript for
## Hooks: blocks and summarize them:
## Recent Hook Executions (this session)
| Hook | Actions | Status |
|------|---------|--------|
| post-task | sync, commit, detect-spike, capture-knowledge | success |
| pre-task | check-blockers, suggest-skills, setup-worktree | success |
| pre-session | verify-clean | warning |
Persistent side effects worth checking: .pokayokay/wip-state.json (WIP
tracking), .pokayokay/pokayokay-review-failures.json (review failure
tracking), .claude/rules/pokayokay/ (graduated rules).
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.
- 2d ago First seen · 145 lines · 5 tokens per session scan A c1b297f4e267
hooks is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 1,580 once invoked, about $0.0000 per session on Opus 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-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.