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/egzonarifi/povio-worklog-mcp/cursorrulesgit clone --depth 1 https://github.com/EgzonArifi/povio-worklog-mcpWrote 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/egzonarifi/povio-worklog-mcp/cursorrules)<a href="https://agentmods.dev/rules/egzonarifi/povio-worklog-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/egzonarifi/povio-worklog-mcp/cursorrules.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.00429 | $0.00429 |
| Opus 5 | $0.00215 | $0.00215 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
cursorrules 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 4d 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
Povio Worklog Shortcuts
Quick Command Patterns
When I use these patterns, interpret them as MCP tool calls:
List Projects
- "wl list" → list_povio_projects
- "projects" → list_povio_projects
Generate Worklog
- "wl" → generate_worklog for today
- "wl today" → generate_worklog for today
- "wl yesterday" → generate_worklog for yesterday
- "wl [YYYY-MM-DD]" → generate_worklog for specific date
Post Worklog
- "wl post [hours]" → generate_and_post_worklog with default project
- "wl post [project] [hours]" → generate_and_post_worklog with specific project
- "post [hours] to [project]" → post_worklog
Combined (Generate + Post)
- "wl [project] [hours]" → generate_and_post_worklog Example: "wl FaceFlip 8" → generate for today, post to FaceFlip, 8 hours Example: "wl Autobiography 4" → generate for today, post to Autobiography, 4 hours
Common Patterns
- "wl yesterday FaceFlip 6" → generate yesterday's worklog, post to FaceFlip, 6 hours
- "wl 2024-10-28 FaceFlip 8" → generate specific date worklog (Oct 28), post to FaceFlip, 8 hours
- "wl list then post 8" → list projects, then generate and post 8 hours to selected
Project Name Shortcuts
Common project names for quick reference:
- FaceFlip (ID: 15886)
- Autobiography (ID: 14093)
- "Povio Estimations" (ID: 14004)
- "Bunny CDN Mobile" (ID: 13802)
- "Team Leads" (ID: 13396)
- "iOS Internal" (ID: 13247)
Always use the povio-worklog MCP server tools for these commands.
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.
- 4d ago First seen · 43 lines · 429 tokens per session scan A 06f4415bb8fb
cursorrules is a cursor rule published in the GitHub repository EgzonArifi/povio-worklog-mcp (2 stars, last pushed 10mo ago), licensed MIT. It adds 429 tokens to every session, about $0.0021 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
state-memory-mcp
This project tracks workflow state, tasks, design decisions, and blockers using state-memory-mcp with project slug "state-memory-mcp".
903-story-template
ALWAYS use when creating or updating story files to ensure proper tracking and implementation. This rule enforces consistent story structure with tasks, context, and progress tracking.
cursor_conductor_task_management
description: Best practices for effective task management with Conductor Tasks in an AI-assisted workflow globs: / alwaysApply: true.
cursorrules
When the user asks about project management, use project-management-ai-mcp tools: decomposetask, plansprint, assessrisks, estimatetimeline, generatestandup.
process-task-list
Guidelines for managing task lists in markdown files to track progress on completing a PRD.
awp-auto
When the user says awp auto, awp auto strict, or runs the Kanban Auto command — enforce the per-task loop (not batch delivery).