task-rule

A test rule for management tasks. The description does not provide enough detail to explain any specific behavior beyond that.

In plain words
What is it for?
The provided information is too limited to identify a concrete job for it.
Why use it?
It may document a management-task rule, but the available information does not say what problem it solves.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/fireharp/cursor-rules/task-rule
Clone the repo
git clone --depth 1 https://github.com/fireharp/cursor-rules
Per session 32 This file is loaded in full into every session.
When invoked 32 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00032
Opus 5 $0.00016 $0.00016
Sonnet 5 $0.00006 $0.00006
Haiku 4.5 $0.00003 $0.00003

Measured yesterday against content hash ae335b29099c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

task-rule 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 yesterday.

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.

test-rules/mgmtn/tasks/task-rule.mdc · 6 lines

What it actually says

Management Task Rule

This is a test rule for management tasks.

Rule Name: mgmtn/tasks/task Description: A test rule for task management

Changes

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.

  1. yesterday First seen · 6 lines · 32 tokens per session scan A ae335b29099c

Subscribe to this mod's changes

task-rule is a cursor rule published in the GitHub repository fireharp/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 32 tokens to every session, about $0.0002 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.