MultiPost-Extension is a browser extension that publishes text, images, videos, and other content to multiple social media platforms from one operation. Content creators use it to distribute a single piece of content across supported platforms, and web applications or scripts can call its extension or REST APIs.
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/leaperone/MultiPost-ExtensionWrote 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/leaperone/multipost-extension/i18n)<a href="https://agentmods.dev/rules/leaperone/multipost-extension/i18n"><img src="https://agentmods.dev/badge/rules/leaperone/multipost-extension/i18n/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/leaperone/multipost-extension/i18n"><img src="https://agentmods.dev/badge/rules/leaperone/multipost-extension/i18n.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.00000 | $0.00324 |
| Opus 5.5 | $0.00000 | $0.00130 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
i18n 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
Internationalization (i18n) Guidelines:
Message Structure:
- Store all text content in
/locales/[locale]/messages.json - Use descriptive message keys in camelCase:
errorImportingContent - Include placeholders with $PLACEHOLDER$ syntax
- Add descriptions for translators in message files
console.logdon't need add i18n, only for UI text display on screen
Message Format:
"extensionDisplayName": {
"message": "MultiPost",
"description": "Multipost Extension"
},
Implementation:
- Use
chrome.i18n.getMessage('extensionDisplayName')for all user-facing text - Never hardcode text strings in UI components
- Handle RTL languages with appropriate CSS
- Set default_locale in manifest.json
- Support fallback locales
Best Practices:
- Keep messages concise and clear
- Use semantic keys (e.g., WELCOME_MESSAGE vs MSG_001)
- Maintain consistent terminology across translations
- Handle pluralization properly
- Consider cultural differences in formatting dates, numbers, and currencies
- Test UI with different language lengths
Code Examples:
// Component usage
const message = chrome.i18n.getMessage("WELCOME_MESSAGE", [username]);
// Manifest configuration
{
"default_locale": "en",
"name": "__MSG_extension_name__",
"description": "__MSG_extension_description__"
}
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 · 50 lines · 0 tokens per session scan A 663569d1fa2d
i18n is a cursor rule published in the GitHub repository leaperone/MultiPost-Extension (3,691 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 324 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-09-04.
Other cursor rules, from other repositories
report
A set of rules for generating HTML dashboards that present data and analysis in Korean. It defines the required page structure, visual libraries, fonts, and report content.
controlflow-docs-evals
Rules for documentation parity, localized tutorials, and eval verification.
frontend-translation-management
Maintain consistent translation practices across the frontend application to ensure proper internationalization and user experience.
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.