consumer-surfaces

A rule file about the parts of a product that users or other systems interact with.

In plain words
What is it for?
It is for projects that maintain guidance about consumer-facing interfaces or integration points.
Why use it?
It can keep changes focused on the right user-facing or system-facing surfaces, although the excerpt gives no detailed instructions.

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/consumer-surfaces
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 yesterday against content hash 2bd739292f2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

consumer-surfaces 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.

.cursor/rules/consumer-surfaces.mdc · 1 lines

What it actually says

../../.agents/rules/consumer-surfaces.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 · 1 lines · 10 tokens per session scan A 2bd739292f2d

Subscribe to this mod's changes

consumer-surfaces 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.