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/AlphaBitCore/nexus-gatewayWrote 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/alphabitcore/nexus-gateway/token-field-stamp-sweep)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/token-field-stamp-sweep"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/token-field-stamp-sweep.svg" alt="Measured on agentmods" 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.00000 | $0.00470 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
token-field-stamp-sweep 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 8d 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
Token-field stamp sweep (binding)
You are editing AI Gateway provider / proxy code. Adding a new usage / token field requires 5 stamp sites, not just the obvious one. Missing the 4 cache-side sites = all prod cache traffic NULL on the new column. Memory anchor: [[feedback_token_field_handler_sweep]].
Read docs/developers/architecture/services/ai-gateway/provider-adapter-architecture.md §5 BEFORE editing.
The 5 stamp sites
handleNonStream— non-streaming response path.handleStream— streaming response path (at stream end).proxy_cache.go:cacheStoreNonStream— cache write path for non-streaming.proxy_cache.go:cacheStoreStream— cache write path for streaming.proxy_cache.go:cacheRead*— cache read path (deserialise the stamped value).
Checklist when adding a token field
- Field added to
Usagestruct inproviders/types.go. - Column added to
traffic_eventschema (Prisma + migration). - Stamped in
handleNonStream. - Stamped in
handleStream. - Stamped in
cacheStoreNonStream. - Stamped in
cacheStoreStream. - Deserialised in
cacheRead*. - Unit test exercises both non-stream and stream cache paths.
- Smoke test confirms the new column is non-NULL after a cache hit + cache miss.
Why it matters
The cache paths are easy to forget — they share the data layout with the live paths but live in proxy_cache.go, a separate file. Stamping handleNonStream only is the canonical mistake; cache traffic then writes NULL for the new column and the failure is silent until an analytics dashboard notices.
Skipping this rule requires explicit user approval in chat.
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.
- 8d ago First seen · 40 lines · 0 tokens per session scan A 262b4bb57639
token-field-stamp-sweep is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 470 tokens. 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-30.
Other cursor rules, from other repositories
skill-mcp-server
Padrões DARE para servidores MCP (Model Context Protocol da Anthropic) em TypeScript ou Python. Tools, resources, prompts; transports stdio/SSE/HTTP; validação Zod/Pydantic; autorização por tool; observabilidade; testes; publicação.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.