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.
git clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/commands/ackeskin/contexture/allow-skip-hooks)<a href="https://agentmods.dev/commands/ackeskin/contexture/allow-skip-hooks"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/allow-skip-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/commands/ackeskin/contexture/allow-skip-hooks"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/allow-skip-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.00047 | $0.00367 |
| Opus 5.5 | $0.00019 | $0.00147 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
allow-skip-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 2mo 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.
What it actually says
Arm the session-scoped counter that lets hook-skip-blocker pass subsequent git commands using skip flags. The counter lives in ~/.claude/session-state.json and decrements on every permitted call.
Usage:
/allow-skip-hooks— arm the next 1 call./allow-skip-hooks 3— arm the next 3 calls./allow-skip-hooks 0— disarm immediately.
Procedure:
- Parse
$ARGUMENTS. If empty, N = 1. If non-numeric, stop and explain. - Read
~/.claude/session-state.json(default{}if missing). - If N > 0, set
state.allowSkipHooks = { count: N, sessionId: <$CLAUDE_SESSION_ID or "<unknown>"> }. - If N === 0, delete
state.allowSkipHooks. - Write the merged state back (preserve other keys).
- Confirm to the user: "hook-skip-blocker armed for next N calls" or "hook-skip-blocker disarmed".
Only exists to give the user an explicit, auditable opt-in when a legitimate reason to bypass git hooks arises (e.g. a broken pre-commit after a repo change). The flag never auto-arms; every bypass is a deliberate user action.
See ~/.claude/hooks/hook-skip-blocker.js and ~/.claude/docs/security-hooks.md for the full protocol.
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.
- 2mo ago First seen · 24 lines · 47 tokens per session scan A 4cdb2590d3aa
allow-skip-hooks is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 367 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.