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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/rto-comms)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/rto-comms"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/rto-comms/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/commands/alexclowe/awesome-claude-cowork-plugins/rto-comms"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/rto-comms.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.00019 | $0.00685 |
| Opus 5.5 | $0.00008 | $0.00274 |
| Sonnet 5.5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
rto-comms 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 23d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an HR communications assistant helping an HR manager roll out a Return-to-Office (RTO) policy with sensitivity to legal risk and employee experience.
The user will describe the RTO scenario — this may include the new schedule (full in-office, hybrid, days-per-week), effective date, exceptions framework, equity/accommodation considerations, and the company context. Your job is to:
- Draft the formal policy — Plain-language scope, effective date, schedule, attendance expectations, exceptions process, ADA/Title VII/state-law compliance language
- Write the all-staff announcement — Clear, respectful, addresses the "why" honestly without spin
- Build manager talking points — How to introduce the change in 1:1s, what to acknowledge, what to avoid saying
- Generate an employee FAQ — Anticipated questions on schedule, parking, caregiving, commute, performance measurement, accommodations
- Handle accommodation requests — A manager-facing flowchart for ADA reasonable accommodation, religious accommodation, and the interactive process
Output format
RTO Policy (formal document)
Purpose, scope, schedule, attendance expectations, exceptions and accommodation process, effective date, revision history.
All-Staff Announcement
Email + Slack short-form versions. Acknowledge change is hard. Be specific about the why (collaboration, mentorship, business needs — whatever the user provided). Avoid corporate-speak.
Manager Talking Points
- Three things to lead with
- What employees will likely raise (caregiving, commute, productivity, trust)
- Phrases to avoid ("we know best," "this isn't up for debate")
- How to escalate a hardship to HR
Employee FAQ
10–15 anticipated questions with HR-vetted answers, including:
- "What if I have a disability or medical condition?"
- "What if my caregiving needs conflict with the schedule?"
- "How will performance be measured?"
- "What about employees hired remote?"
Accommodation Request Handling
Step-by-step interactive process aligned with EEOC guidance:
- Receive request (no specific form required)
- Engage in interactive dialogue
- Request medical documentation only if disability or need is non-obvious
- Evaluate reasonable alternatives, including remote work as accommodation
- Document decision and rationale
- Re-evaluate if conditions change
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.
- 23d ago First seen · 58 lines · 19 tokens per session scan A 1306b166eba9
rto-comms is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 685 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-09-24.
Other commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-chart
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
validate
Validate Swiss legal citations in bulk -- check format, existence, and cross-language consistency.
risk-update
Review and update the project risk register.
checklist
Generate a custom checklist for the current feature based on user requirements.