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 agentmods add skills/glincker/glin-profanity/profanity_checknpx skills add glincker/glin-profanity --skill profanity_checkgit clone --depth 1 https://github.com/glincker/glin-profanityWrote 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/glincker/glin-profanity/profanity_check)<a href="https://agentmods.dev/skills/glincker/glin-profanity/profanity_check"><img src="https://agentmods.dev/badge/skills/glincker/glin-profanity/profanity_check.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00430 |
| Opus 5 | $0.00008 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
profanity_check 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 4d 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
Profanity Check Skill
When the user asks you to check a message for profanity, or when you need to
verify content before sending, use the check_profanity tool.
When to Use
- User asks "is this message appropriate?"
- User says "check this for profanity"
- Before sending messages to external platforms
- When moderating user-generated content
How to Use
- Call the
check_profanitytool with the text to check - If
containsProfanityis true, warn the user - Suggest alternatives if profanity is found
Example Response
If profanity is detected: "I found some inappropriate language in your message. The words [words] were flagged. Would you like me to suggest alternatives?"
If clean: "Your message looks good! No inappropriate content detected."
Multi-language Support
This skill supports 24 languages. Specify languages parameter if checking non-English content:
languages: ["english", "spanish"]for multi-language- Default is English only
Supported Languages
arabic, chinese, czech, danish, dutch, english, esperanto, finnish, french, german, hindi, hungarian, italian, japanese, korean, norwegian, persian, polish, portuguese, russian, spanish, swedish, thai, turkish
Notes
- Detects leetspeak (e.g., "f0ck" → "fuck")
- Detects unicode obfuscation (e.g., "fück" → "fuck")
- Context-aware: "kick ass" in gaming is OK, offensive use is flagged
Credits
Powered by glin-profanity
Compatible with OpenClaw, Moltbot (legacy), and Clawdbot (legacy).
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.
- 4d ago First seen · 59 lines · 16 tokens per session scan A 12f7c14ab093
profanity_check is a skill published in the GitHub repository glincker/glin-profanity (60 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 430 once invoked, about $0.0001 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-30.
Other skills, from other repositories
start9-frontend
Start9 house style for every Angular + Taiga UI web frontend (StartOS ui/setup-wizard, StartWRT, StartTunnel, brochure-marketplace, start9-store, ops-server, support-server). Use BEFORE writing or reviewing any frontend code in these apps — components, templates, styles/CSS, forms, dialogs/toasts, routing, state, DI…
opendia-harness
Install, configure, and troubleshoot OpenDia for Grok Build (and other MCP harnesses). Use when setting up the plugin, config.toml MCP entry, ports, extension disconnects, tool timeouts, or tunnel mode.
opendia
Drive the user's real browser through OpenDia MCP (logged-in sessions, cookies, wallets, bookmarks, history). Use when automating Chrome/Firefox for social posts, form fills, multi-tab research, local webapp testing, or any task that needs the user's existing browser profile — not a disposable cloud browser.
huly-cli
Operate Huly through the @firfi/huly-cli executable. Use when a coding agent needs to authenticate, switch Huly workspaces or projects, discover commands, query structured Huly data, or perform confirmed Huly mutations from a shell or automation workflow.
pixi-vn-getting-started
Use when setting up a new or existing project on @drincs/pixi-vn, wiring the main.ts entry point, or calling the top-level Game API (Game.init, Game.start, Game.onEnd, Game.addOnError, Game.onNavigate, Game.clear) — this is the entry point every Pixi'VN project needs before touching canvas, narration, sound, storage…
pixi-vn-migration
Use when upgrading an existing @drincs/pixi-vn project to a newer version, or when a runtime/type error matches a known breaking change. Covers every breaking change between versions with before/after code.