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/winsenlabs/platosWrote 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/winsenlabs/platos/writing-tasks)<a href="https://agentmods.dev/rules/winsenlabs/platos/writing-tasks"><img src="https://agentmods.dev/badge/rules/winsenlabs/platos/writing-tasks/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/rules/winsenlabs/platos/writing-tasks"><img src="https://agentmods.dev/badge/rules/winsenlabs/platos/writing-tasks.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.07920 | $0.07920 |
| Opus 5.5 | $0.03168 | $0.03168 |
| Sonnet 5.5 | $0.01584 | $0.01584 |
| Haiku 4.5 | $0.00792 | $0.00792 |
Grade A, and why
writing-tasks 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 2mo 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.
This is a copy
100% identical to writing-tasks — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
globs: /trigger//.ts, /trigger//.tsx,/trigger//.js,/trigger//.jsx description: Guidelines for writing Trigger.dev tasks alwaysApply: false
How to write Trigger.dev tasks
Overview of writing a Trigger.dev task
- Run the CLI
initcommand:npx trigger.dev@latest init. - Create a Trigger.dev task.
- Set up any environment variables.
- Run the Trigger.dev dev command:
npx trigger.dev@latest dev.
Essential requirements when generating task code
- You MUST import from
@trigger.dev/sdk(NEVER@trigger.dev/sdk/v3) - You MUST NEVER use
client.defineJob - YOU MUST
exportevery task, including subtasks - If you are able to generate an example payload for a task, do so.
🚨 CRITICAL INSTRUCTIONS FOR AI LANGUAGE MODELS 🚨
As an AI language model, you MUST NOT generate any of the following code patterns, as they are DEPRECATED and will BREAK the application:
// ❌ NEVER GENERATE THIS CODE - IT WILL BREAK THE APPLICATION
client.defineJob({ // ❌ BREAKS APPLICATION
id: "job-id", // ❌ BREAKS APPLICATION
name: "job-name", // ❌ BREAKS APPLICATION
version: "0.0.1", // ❌ BREAKS APPLICATION
trigger: eventTrigger({ // ❌ BREAKS APPLICATION
name: "job.trigger", // ❌ BREAKS APPLICATION
schema: z.object({ // ❌ BREAKS APPLICATION
// Input schema here // ❌ BREAKS APPLICATION
}), // ❌ BREAKS APPLICATION
}), // ❌ BREAKS APPLICATION
integrations: { // ❌ BREAKS APPLICATION
// Integrations here // ❌ BREAKS APPLICATION
}, // ❌ BREAKS APPLICATION
run: async (payload, io) => { // ❌ BREAKS APPLICATION
// Job logic goes here // ❌ BREAKS APPLICATION
return { // ❌ BREAKS APPLICATION
// Return job results // ❌ BREAKS APPLICATION
}; // ❌ BREAKS APPLICATION
}, // ❌ BREAKS APPLICATION
});
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.
- 2mo ago First seen · 1,248 lines · 7,920 tokens per session scan A 6327abf77deb
writing-tasks is a cursor rule published in the GitHub repository winsenlabs/platos (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7,920 tokens to every session, about $0.0317 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to writing-tasks, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
020-flask
Flask API Gateway conventions for LMForge.
ddd-design-guide
Apply when designing or refactoring domain models, services, stores, or discussing DDD (Domain-Driven Design) architecture. Also apply when working on business logic layers, API modules, or planning domain boundaries and migrations.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
service-bindings
Worker-to-Worker RPC - bindings.worker() by name, WorkerEntrypoint callee, typed RPC deferred, requestId propagation.
boundaries
Package dependency boundaries - tag map and enforced invariants.
rulesforconvex
description: Convex guidelines globs: alwaysApply: true.