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 tomzx/agents --skill create-messagegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-message)<a href="https://agentmods.dev/skills/tomzx/agents/create-message"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-message/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/tomzx/agents/create-message"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-message.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.00027 | $0.00907 |
| Opus 5.5 | $0.00011 | $0.00363 |
| Sonnet 5.5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
create-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 22d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Message
Takes a draft message and improves it by removing negative tone, reformulating with positive language, and appending actionable suggestions where appropriate.
Prerequisites
- Draft message: The message the user wants to send (provided inline or in a file)
- Recipient (optional): Who the message is for (e.g., "a colleague", "a manager", "a client"), used to calibrate tone
- Context (optional): Any background that helps understand the intent (e.g., "they missed a deadline", "I want to decline a meeting")
- Apply the shared communication guidelines in
skills/communication-guidelines/SKILL.mdwhen rewriting for concision.
Steps
- Read the draft message carefully and identify the core intent.
- Scan for negative tone markers: passive-aggression, blame, criticism without constructive framing, defensiveness, dismissiveness, or vague complaints.
- Reformulate each negative passage using positive language that preserves the original intent.
- Identify any places where actionable suggestions would strengthen the message, and add them.
- Review the revised message for tone consistency, clarity, and brevity.
Tone Rewrite Rules
Remove:
- Blame language ("you failed to", "you didn't", "you never")
- Passive-aggressive framing ("as I'm sure you're aware", "per my last email")
- Vague complaints ("this isn't good enough", "this needs to be better")
- Defensiveness ("I was just trying to", "that's not what I meant")
- Dismissive language ("whatever you think", "it doesn't matter to me")
- Sarcasm or backhanded compliments
Replace with:
- Ownership language ("I'd like us to", "we could", "I suggest")
- Specific, observable descriptions ("the report arrived on Friday, past the Wednesday deadline" instead of "you were late again")
- Constructive framing ("here's what would help", "moving forward, I'd recommend")
- Direct requests ("could you", "would it be possible to")
- Collaborative tone ("let's", "how about we")
Actionable Suggestions
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.
- 22d ago Changed · +3 lines a5cf2d0e60af
- 23d ago Changed · -4 lines 07b3c70ebe84
- 28d ago Changed · +1 lines 1137b504f436
- 2mo ago First seen · 91 lines · 27 tokens per session scan A 537fdd6d7103
create-message is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 907 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…