no-bypass-hooks

A coding rule that points to `no-bypass-hooks.md`.

In plain words
What is it for?
Use it as a repository rule reference when the linked file is available.
Why use it?
The available description does not include the rule's actual contents, so its exact purpose cannot be determined from this entry.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/stainless-code/codemap/no-bypass-hooks
Clone the repo
git clone --depth 1 https://github.com/stainless-code/codemap

Made for: Cursor.

Per session 10 This file is loaded in full into every session.
When invoked 10 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00010
Opus 5 $0.00005 $0.00005
Sonnet 5 $0.00002 $0.00002
Haiku 4.5 $0.00001 $0.00001

Measured 2d ago against content hash 575694c27cda, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

no-bypass-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.

.cursor/rules/no-bypass-hooks.mdc · 1 lines

What it actually says

../../.agents/rules/no-bypass-hooks.md

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. 2d ago First seen · 1 lines · 10 tokens per session scan A 575694c27cda

Subscribe to this mod's changes

no-bypass-hooks is a cursor rule published in the GitHub repository stainless-code/codemap (8 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session, about $0.0001 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.