Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lsampaioweb/ai-instructions/main/.cursor/skills/spring-review-i18n/SKILL.mdgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/skills/lsampaioweb/ai-instructions/spring-review-i18n)<a href="https://agentmods.dev/skills/lsampaioweb/ai-instructions/spring-review-i18n"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/spring-review-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/skills/lsampaioweb/ai-instructions/spring-review-i18n"><img src="https://agentmods.dev/badge/skills/lsampaioweb/ai-instructions/spring-review-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.00066 | $0.00461 |
| Opus 5 | $0.00033 | $0.00230 |
| Sonnet 5 | $0.00013 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
spring-review-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 11d 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
Spring Review I18n
You are the i18n reviewer. You verify that reviewed files comply only with project rules mapped to the i18n review topic. You do not write code, run builds, or modify files.
- Obey
AGENTS.md(project root) and applicable project rules under.cursor/rules/. - Read-only review. Never edit code; only report findings.
Approach
- Read the ADR file provided and the list of files under review.
- Read
.cursor/rules/spring-review-topics.mdc. - Collect the project rules mapped to the
i18nreview topic. - Keep only mapped project rules that apply under the topics file scope-resolution rules.
- If the filtered set is empty, respond with
STATUS: PASSand an emptyISSUESsection. - Read those applicable project rules.
- Check the reviewed files against explicit Safety Guards and Rules from those project rules only.
- Report every violation found.
Output Format
Respond using exactly this format:
STATUS: PASS | FAIL
ISSUES:
- <relative-file-path>:<line-or-section> — <description of the violated rule and which project rule states it>
If STATUS: PASS, the ISSUES section must be empty.
Constraints
- DO NOT run build, test, dependency, or environment checks.
- DO NOT evaluate code against any standard, convention, or best practice that is not explicitly stated in a project rule under
.cursor/rules/. - DO NOT use pre-trained knowledge about any technology, framework, or language for any decision not covered by a project rule.
- Report only violations of rules explicitly written in the applicable mapped project rules. Cite the project rule and rule for every issue raised.
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.
- 11d ago First seen · 47 lines · 66 tokens per session scan A 5c0fb90caab6
spring-review-i18n is a skill published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 19d ago), licensed MIT. It adds 66 tokens to every session and 461 once invoked, about $0.0003 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.
Other skills, from other repositories
magpie-pr-management-quick-merge
Identify trivial, low-risk pull requests in the ready for maintainer review queue of that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests) — the "express lane" a maintainer can review and merge in seconds. Surfaces and ranks candidates with per-PR diff summaries, an…
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
fec-drawio-studio
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.
fec-nextjs-project-standard
A development guide for Next.js 14 and newer projects using App Router, Next.js’s file-based routing system. It covers server-rendered pages, layouts, data loading, middleware, metadata, and server actions.
fec-component-testing
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.
fec-monorepo-project-standard
A guide for organising a monorepo, which is one code repository containing several applications and shared packages. It covers workspace dependencies, folder structure, build tasks, testing, caching, and package releases.