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.
npx skills add parisgroup-ai/imersao-ia-setup --skill spell-check-pt-engit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/spell-check-pt-en)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/spell-check-pt-en"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/spell-check-pt-en/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/parisgroup-ai/imersao-ia-setup/spell-check-pt-en"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/spell-check-pt-en.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.00070 | $0.01544 |
| Opus 5.5 | $0.00028 | $0.00618 |
| Sonnet 5.5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
spell-check-pt-en 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spell Check PT-BR / EN
Overview
The user types fast and often with typos so the assistant moves quickly. That's fine for chat. But typos must NEVER reach files the project ships — UI copy, i18n locales, READMEs, CLI help text, error messages, commit messages, or doc comments (///, JSDoc, docstrings).
Core rule: Before writing/editing text into a file, normalize spelling and accentuation. Preserve the user's tone, voice, capitalization style, and intent. Do not rewrite, expand, or "improve" the prose.
When to Use
Apply BEFORE every Write or Edit that contains prose in PT-BR or EN, including:
- Locale files (
*.json,*.po,messages/*.ts) - UI copy in components (labels, placeholders, button text, toasts, empty states)
- Error messages, validation messages, exception strings
- CLI help text (
clap,commander,argparse) - Public docs: README, CHANGELOG, ADRs, markdown in
docs/ - Doc comments that ship to public reference (rustdoc
///, JSDoc/** */, Python docstrings) - Commit messages and PR titles/descriptions
- Notas e documentação persistidas (ex.: vault, wiki)
When NOT to Use
- Chat replies to the user (keep them fast and informal)
- Internal log lines, debug prints, temporary console output
- Variable/function/file names (those follow code conventions, not spelling rules)
- Code identifiers, API field names, DB column names
- User-supplied content quoted verbatim (preserve as-is)
Procedure
- Detect language of the text being written (PT-BR, EN, or mixed).
- Normalize:
- Fix obvious typos (
pra→paraonly in formal copy; keepprain casual brand voice if the surrounding copy is casual). - Restore accents/cedilla in PT-BR (
nao→não,usuario→usuário,acao→ação). - Fix capitalization of proper nouns (
react→React,nextjs→Next.js,postgres→Postgres,ai→AI). - Fix punctuation: missing periods, double spaces, smart-quote consistency within a file.
- Fix obvious typos (
- Preserve:
- The user's chosen tone (formal vs casual). If the file already uses
você, keep it; if it usestu, keep it. - Intentional informality in marketing copy or brand voice.
- Domain jargon (see Technical Dictionary below).
- Casing of brand names exactly as the user wrote them when intentional.
- The user's chosen tone (formal vs casual). If the file already uses
- Do not:
- Rewrite sentence structure.
- Expand abbreviations the user chose deliberately.
- Translate between PT and EN.
- Add Oxford commas or change style choices already consistent in the 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.
- 21d ago First seen · 125 lines · 70 tokens per session scan A 89d11309a9c5
spell-check-pt-en is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 20d ago), licensed MIT. It adds 70 tokens to every session and 1,544 once invoked, about $0.0003 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-10-06.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
crossing-the-chasm
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…