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/censor_messagenpx skills add glincker/glin-profanity --skill censor_messagegit clone --depth 1 https://github.com/glincker/glin-profanityWhat 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.00375 |
| Opus 5 | $0.00008 | $0.00187 |
| Sonnet 5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
censor_message 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 2d 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
Censor Message Skill
When the user wants to send a message but have profanity automatically
censored, use the censor_text tool.
When to Use
- User says "censor this message"
- User wants to share content but remove bad words
- Preparing content for family-friendly platforms
- Moderating user content before posting
How to Use
- Call the
censor_texttool with the text - Return the censored version
- Optionally show what was censored
Parameters
text: The text to censorreplacement: Custom replacement (default: "***")languages: Array of languages to check
Example
Input: "What the fuck is this shit?" Output: "What the *** is this ***?"
Custom Replacements
Users can specify custom replacement strings:
- "[CENSORED]" for formal documents
- "****" for standard
- "" (empty) to remove entirely
- "[REDACTED]" for official-looking documents
Multi-language Support
Works with 24 languages. For non-English content, specify:
languages: ["spanish", "portuguese"]
Platform Integration
This skill works across all OpenClaw-supported platforms:
- Telegram
- Discord
- Slack
- iMessage
- And more...
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.
- 2d ago First seen · 68 lines · 16 tokens per session scan A 6a3ccb8f6086
censor_message is a skill published in the GitHub repository glincker/glin-profanity (59 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 375 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.