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/inakianduaga/clockify-mcp/plangit clone --depth 1 https://github.com/inakianduaga/clockify-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/inakianduaga/clockify-mcp/plan)<a href="https://agentmods.dev/rules/inakianduaga/clockify-mcp/plan"><img src="https://agentmods.dev/badge/rules/inakianduaga/clockify-mcp/plan.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.00774 | $0.00774 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
plan 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
description: Always include these rules. globs: alwaysApply: true
Before every Plan/Architect task ALWAYS do 3 things:
a. Read the existing documentation in docs/ : i. docs/architecture.md, ii. docs/product_requirement_docs.md, iii. docs/technical.md
b. Read the plans and related task planning & context in tasks/: i. tasks/active_context.md, ii. tasks/tasks_plan.md
c. Get required solution conytext from the code files in src and other codes at other places.
- Below is the Planning Workflow to follow:
- UNDERSTAND the REQUIREMENTS:
- Always ask for clarifications and follow-ups.
- Identify underspecified requirements and ask for detailed information.
- Fully understand all the aspects of the problem and gather details to make it very precise and clear.
- Ask towards all the hypothesis and assumptions needed to be made. Remove all the ambiguities and uncertainties.
- Suggest solutions that I didn't think about, i.e. anticipate my needs and things to be specified.
- Only after having hundred percent clarity and confidence, proceed for SOLUTION.
- FORMULATING the SOLUTION:
- SOLUTION VALIDATION:
After every Plan/Architect task ALWAYS do 2 things:
a. Document the plan into existing documentation and update files in docs/ : i. docs/architecture.md, ii. docs/product_requirement_docs.md, iii. docs/technical.md
b. Document the plans and related task planning & context in tasks/: i. tasks/active_context.md, ii. tasks/tasks_plan.md
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 · 75 lines · 774 tokens per session scan A beea2c3cc4f5
plan is a cursor rule published in the GitHub repository inakianduaga/clockify-mcp (14 stars, last pushed 1y ago), licensed MIT. It adds 774 tokens to every session, about $0.0039 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.