cursorrules

Repository rules stating that AGENTS.md contains the authoritative collaboration guidance and docs/HANDOFF.md contains the current task status.

In plain words
What is it for?
Use them when working in the b2b-sdr-hermes-skill repository and following its specified continuation and wrap-up procedures.
Why use it?
They direct contributors to the project’s required instructions before starting work.

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/ipythoning/b2b-sdr-hermes-skill/cursorrules
Clone the repo
git clone --depth 1 https://github.com/iPythoning/b2b-sdr-hermes-skill

Made for: Cursor.

Per session 54 This file is loaded in full into every session.
When invoked 54 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00054 $0.00054
Opus 5 $0.00027 $0.00027
Sonnet 5 $0.00011 $0.00011
Haiku 4.5 $0.00005 $0.00005

Measured yesterday against content hash c15275e000eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 yesterday.

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.

Origin

This is a copy

100% identical to cursorrules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursorrules · 3 lines

What it actually says

本仓库的权威协作守则是 AGENTS.md;当前任务状态见 docs/HANDOFF.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. yesterday First seen · 3 lines · 54 tokens per session scan A c15275e000eb

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository iPythoning/b2b-sdr-hermes-skill (39 stars, last pushed 12d ago), licensed MIT. It adds 54 tokens to every session, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.