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/chooomedia/keymojiWrote 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/chooomedia/keymoji/core)<a href="https://agentmods.dev/rules/chooomedia/keymoji/core"><img src="https://agentmods.dev/badge/rules/chooomedia/keymoji/core/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/chooomedia/keymoji/core"><img src="https://agentmods.dev/badge/rules/chooomedia/keymoji/core.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.00528 | $0.00528 |
| Opus 5.5 | $0.00211 | $0.00211 |
| Sonnet 5.5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
core 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 1mo 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
Keymoji — Core Rules
Keymoji ist eine Svelte-Anwendung für sichere Emoji-Passwort-Generierung mit Magic-Link-Auth (OTP per E-Mail), Account-Management via n8n/Google Sheets und AI Story Mode.
Code-Qualität
- IMMER TypeScript — alle neuen Dateien müssen
.tsoderlang="ts"sein - DRY — keine Duplikate, wiederverwendbare Komponenten/Utils
- Single Source of Truth — jede Datenquelle hat genau einen Ort
- Performance First — Funktionen nur so oft wie nötig ausführen
- Memory Leaks — alle Timeouts/Intervals in
onDestroyclearen - Keine
anyTypes — immer spezifische TypeScript-Types
Verbotene Patterns
- Direkte
fetch()Calls — immercachedFetchausutils/apiCache.js - Klassische Svelte Stores wo Runes möglich
- Inline Styles — nur Tailwind CSS
- Doppelte API-Calls — Daten zwischen Komponenten weitergeben
- Console Logs in Production — nur via
isDevelopment() - Magic Numbers — immer Konstanten
- Nested Ternaries — klarere If-Statements
- Unused Imports
Naming Conventions
- Komponenten:
PascalCase(UserSettings.svelte) - Dateien/Funktionen:
camelCase(accountStore.js,getUserSettings()) - Konstanten:
UPPER_SNAKE_CASE(STORAGE_KEYS) - Types/Interfaces:
PascalCase(UserAccount)
Datei-Struktur
src/
├── components/ # A11y/, Core/, Features/, Layout/, UI/
├── config/ # api.js, storage.js, limits.js
├── data/ # languages/, userSettings.json
├── routes/ # Page-Komponenten
├── stores/ # accountStore, dailyUsageStore, userDataStore
├── types/ # Account.ts, ...
└── utils/ # apiCache, metadataCleaner, seo, ...
Aktuelle Prioritäten
- Svelte 5 Runes überall
- TypeScript in allen Dateien
- Keine doppelten API-Calls
- Performance & Caching
- Vollständige A11y
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.
- 1mo ago First seen · 57 lines · 528 tokens per session scan A b46df08d6354
core is a cursor rule published in the GitHub repository chooomedia/keymoji (2 stars, last pushed 3mo ago), licensed MIT. It adds 528 tokens to every session, about $0.0021 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-08-31.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.