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 rules/hlalljie/agent-workflow-presets/communicationgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/rules/hlalljie/agent-workflow-presets/communication)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/communication"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/communication.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.00315 | $0.00315 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
communication 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 3d 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
- Answer before code. If a question needs no code, answer it — don't start coding.
- Discussion vs implementation: if user asks a question or proposes an idea, discuss only. Do not write code until explicit go-ahead.
- Address all numbered points. End with a numbered summary matching original points if the response is long. Never skip a point.
- Restate what was done at the bottom of every response. Nothing important should only appear mid-response.
- Plan tasks: Follow
.cursor/rules/task-scope.mdc: one### Task Nper message unless the user names multiple task numbers (or batchable + explicit batch ask). Do not "helpfully" do the next task. - One reviewable change-set at a time where possible. Wait for review before unrelated follow-ups.
- Explain reasoning when suggesting tools or frameworks. No arbitrary technology choices.
- Don't ask questions with obvious answers from context.
- No excessive console logs. No emoji unless asked.
- When the user points out a rule or instruction wasn't followed, don't just fix the output and move on. Find the rule that should have caught it, identify if it's missing or unclear, and suggest a fix. Do not make changes — present the issue and proposed solution, then wait.
- Git safety:
.cursor/rules/git-safety.mdc. - Never use the AskQuestion tool. Never. Ask questions as plain numbered sentences when needed. Do not ask questions whose answers are already in the conversation.
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.
- 3d ago First seen · 18 lines · 315 tokens per session scan A 384aa12287ff
communication is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 315 tokens to every session, about $0.0016 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-31.
Other cursor rules, from other repositories
x402-coding
@dexterai/x402 SDK conventions and hosted-only OpenDexter tool usage.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).
pn-babylon
Babylon.js scene structure, disposal, and performance. Use when editing Babylon.js or 3D scene code.
pn-astro
Astro conventions: islands, SSG, client directives. Use when editing .astro files. For React components used as Astro islands, pn-react also applies.
pn-plugin-quality-gates
Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.
collate
你在 collate 插件环境下工作。这是一个中文历史文献 OCR + 校对工具包，完整契约见 AGENTS.md。.