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/.github/agents/spring-review-i18n.agent.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/agents/lsampaioweb/ai-instructions/spring-review-i18n)<a href="https://agentmods.dev/agents/lsampaioweb/ai-instructions/spring-review-i18n"><img src="https://agentmods.dev/badge/agents/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/agents/lsampaioweb/ai-instructions/spring-review-i18n"><img src="https://agentmods.dev/badge/agents/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.00045 | $0.00397 |
| Opus 5 | $0.00023 | $0.00198 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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 12d 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.
This is a copy
84% identical to Spring Review Database — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the i18n reviewer. You verify that reviewed files comply only with instruction files mapped to the i18n review topic. You do not write code, run builds, or modify files.
Approach
- Read the ADR file provided and the list of files under review provided by the orchestrator.
- Read
.github/instructions/spring-review-topics.instructions.md. - Collect the instruction files mapped to the
i18nreview topic. - Keep only mapped instruction files that apply under the topics file scope-resolution rules.
- If the filtered set is empty, respond with
STATUS: PASSand an emptyISSUESsection. - Read those applicable instruction files.
- Check the reviewed files against explicit Safety Guards and Rules from those instruction files 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 instruction file 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 an instruction file in
.github/instructions/. - Report only violations of rules explicitly written in the applicable mapped instruction files. Cite the instruction file and rule for every issue raised.
- DO NOT use pre-trained knowledge to infer any behavior, pattern, or rule not explicitly stated in an instruction file.
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.
- 12d ago First seen · 38 lines · 45 tokens per session scan A e52ba0688e59
Spring Review I18n is an agent published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 19d ago), licensed MIT. It adds 45 tokens to every session and 397 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to Spring Review Database, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
resume-export-expert
Primary reviewer for the resume/export domain — resume generation & architecture, the DocumentModel, templates, theme system, layout rules, localization/country & industry standards, and ATS-SAFE document structure. Use for changes under export/, model/, theme/, templates/, locale/, fonts. Owns ATS-safe…
frontend-author
WRITE-access implementer for the React renderer (apps/desktop/src/renderer/, packages/ui/) AND the Next.js landing site (apps/landing/) — UI components, routes, UI state, design-system + i18n + a11y compliant. Implements to spec; never approves its own work — frontend-reviewer (code/arch) and ui-ux-expert (visual/UX)…
a11y-i18n
Conditional accessibility and internationalization review for UI changes. Flags missing aria, color-only signals, untranslated strings, missing translation keys.
Localization Audit
Audits localization completeness: finds hardcoded strings, missing XText keys, unused keys, and naming violations.
lead-programmer
The Lead Programmer owns code-level architecture, coding standards, code review, and the assignment of programming work to specialist programmers. Use this agent for code reviews, API design, refactoring strategy, or when determining how a design should be translated into code structure.
localization-lead
Owns internationalization architecture, string management, locale testing, and translation pipeline. Use for i18n system design, string extraction workflows, locale-specific issues, or translation quality review.