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/laaibaQasim/productivity-kitWrote 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/laaibaqasim/productivity-kit/task-summary)<a href="https://agentmods.dev/rules/laaibaqasim/productivity-kit/task-summary"><img src="https://agentmods.dev/badge/rules/laaibaqasim/productivity-kit/task-summary/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/laaibaqasim/productivity-kit/task-summary"><img src="https://agentmods.dev/badge/rules/laaibaqasim/productivity-kit/task-summary.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.00488 | $0.00488 |
| Opus 5.5 | $0.00195 | $0.00195 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
task-summary 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Summary & Session Logging
Only applies when session_tracking.enabled is true in .cursor/config.json. If it is false or missing, respond normally.
If unsure, read .cursor/config.json before applying the rules below.
Requirements (when session tracking is enabled)
For every task-based response (coding, debugging, feature implementation):
- Always include a summary — no exceptions, regardless of response length
- Skip only for non-coding responses that are 2–3 lines or less
- For coding tasks, add an Implementation Details section before the summary listing key files changed (with line numbers where relevant)
- Summary heading MUST be exactly
**Summary:**— hooks depend on this exact string - Summary length: one paragraph maximum
Coding Task Format
[... response content ...]
**Implementation Details:**
- Updated `src/components/Button.tsx:45-60` to add loading state
**Summary:**
You asked me to [X]. I did [Y].
Session Log (every response)
Append a ### Session Log section at the end of every response. Always include it unless the user explicitly says not to.
Fields:
- User Intent: 1–2 sentence summary of the request
- Prompt Summary: compressed task + constraints + expected outcome
- Provided Context: files, code, or other material the user supplied (summarize, never dump verbatim)
- What I Did: short summary of work completed
- Open Issues: anything unresolved, missing, or uncertain
- Next Best Step: single most useful next action
Keep the log concise. Prefer signal over detail. No filler words.
Example
### Session Log
- **User Intent:** Add a loading state to the Button component.
- **Prompt Summary:** Update Button to show spinner and disable while loading.
- **Provided Context:** Button.tsx snippet provided.
- **What I Did:** Added `loading` prop, updated validate.ts edge case.
- **Open Issues:** No tests updated yet.
- **Next Best Step:** Add unit tests for the loading state.
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.
- 1mo ago First seen · 63 lines · 488 tokens per session scan A ad82d7a9b3aa
task-summary is a cursor rule published in the GitHub repository laaibaQasim/productivity-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 488 tokens to every session, about $0.0020 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 cursor rules, from other repositories
project-context
Current repository context, commands, and documentation authority.
code-conventions
Current TypeScript and contract-change conventions.
api-steps
How to create HTTP endpoints in Motia.
virtual-steps
Connecting nodes virtually and creating a smooth flow in Workbench.
mintlify
You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.