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/kaminari-ad/mcpWrote 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/rules/kaminari-ad/mcp/branding)<a href="https://agentmods.dev/rules/kaminari-ad/mcp/branding"><img src="https://agentmods.dev/badge/rules/kaminari-ad/mcp/branding/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/rules/kaminari-ad/mcp/branding"><img src="https://agentmods.dev/badge/rules/kaminari-ad/mcp/branding.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.00046 | $0.00355 |
| Opus 5.5 | $0.00018 | $0.00142 |
| Sonnet 5.5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
branding 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 today.
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
Branding — Kaminari Ad
The naming bans (never AdVerif in user-facing text, display name vs domain, the grandfathered list) are in core.
Trademark name vs domain
- Display name in copy:
Kaminari Ad— headlines, marketing copy, About pages, footer wordmarks, email subject lines, sales decks. - Domain:
kaminari.ad— URLs, hostnames, email addresses, technical docs.
The dotted form Kaminari.Ad is deprecated. Legacy files carrying it are grandfathered; new user-facing text uses the space form.
Family: Kaminari Ad ↔ Kaminari.Click
Kaminari is a family of two products. Kaminari.Click (https://kaminari.click) is anti-fraud / incoming traffic protection, in a separate repo outside this workspace. Kaminari Ad (https://kaminari.ad) is ad verification — this monorepo.
In marketing copy (landing pages, UI footer, About, sales decks), reference Click as the sister product — "from the team behind Kaminari.Click", "pair with Kaminari.Click". In technical docs (runtime, runbooks, error messages), do not mention Click at all.
Brand identity, inherited from Click: deep eggplant purple background, teal accent, white cards, teal lightning bolts, kanji 雷 watermark. Pricing tiers: Basic / Pro / Enterprise / Threat Intelligence DB.
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.
- today First seen · 24 lines · 46 tokens per session scan A bfe7f3c7caa5
branding is a cursor rule published in the GitHub repository kaminari-ad/mcp (0 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 355 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-11-05.
Other cursor rules, from other repositories
javascript-typescript-code-quality-cursorrules-pro
Cursor rules for JavaScript and TypeScript development with code quality integration.
general-code-quality-and-style
Project-wide rules for readable, maintainable TypeScript code, functional programming, file organization, naming, modular design, reviews, and web performance.
api-design-typescript
API design for TypeScript HTTP services — Express 5, Fastify, NestJS handler patterns, Zod request validation, typed errors with Problem Details, OpenAPI, rate limiting, and CORS. Extends core/rules/api-design.mdc. Applied to route, controller, and handler code.
typescript
TypeScript best practices — strict configuration, advanced type patterns, type safety, generics, branded types, type guards, performance, testing, and common anti-patterns. Applied when working with TypeScript files.
typescript-testing
TypeScript testing guidelines — Vitest/Jest setup, unit testing patterns, mocking strategy, integration testing with Testcontainers, and coverage standards. Applied when working with TypeScript test files.
typescript-security
TypeScript security guidelines — input validation with Zod, JWT handling, SQL injection prevention, secrets hygiene, and dependency scanning. Applied when working with TypeScript files.