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/alkoleft/platform-context-exporterWrote 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/alkoleft/platform-context-exporter/task-tracking-basic)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/task-tracking-basic"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/task-tracking-basic/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/alkoleft/platform-context-exporter/task-tracking-basic"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/task-tracking-basic.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.01141 | $0.01141 |
| Opus 5.5 | $0.00456 | $0.00456 |
| Sonnet 5.5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
task-tracking-basic 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.
This is a copy
100% identical to task-tracking-basic — 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BASIC TASK TRACKING FOR LEVEL 2
TL;DR: This document outlines a streamlined task tracking approach for Level 2 (Simple Enhancement) tasks. It provides a balanced framework for managing task progress with minimal overhead.
🔍 TASK TRACKING OVERVIEW
Level 2 tasks require a more structured tracking approach than Level 1, but don't need the comprehensive tracking of higher-level tasks. This basic tracking system provides sufficient structure while maintaining efficiency.
📋 TASK TRACKING PRINCIPLES
- Clarity: Tasks should be clearly defined
- Visibility: Progress should be visible at a glance
- Structure: Break work into logical subtasks
- Updates: Keep progress regularly updated
- Completion: Clearly mark when tasks are done
📋 TASK STRUCTURE FOR LEVEL 2
## [Feature Name] Enhancement
**Status**: [Not Started/In Progress/Complete]
**Priority**: [High/Medium/Low]
**Estimated Effort**: [Small/Medium/Large]
### Description
[Brief description of the enhancement]
### Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
### Subtasks
- [ ] [Subtask 1]
- [ ] [Subtask 2]
- [ ] [Subtask 3]
### Dependencies
- [Dependency 1]
- [Dependency 2]
### Notes
[Any additional information or context]
📋 TASKS.MD ORGANIZATION
Organize tasks.md with these sections for Level 2 tasks:
# Tasks
## Active Enhancements
- [Enhancement 1] - [Status]
- [Enhancement 2] - [Status]
## Enhancement Details
### [Enhancement 1]
[Task structure as above]
### [Enhancement 2]
[Task structure as above]
## Completed Enhancements
- [X] [Completed Enhancement 1] (YYYY-MM-DD)
- [X] [Completed Enhancement 2] (YYYY-MM-DD)
📋 UPDATING TASK STATUS
Update tasks using this process:
-
Starting a Task:
- Update Status to "In Progress"
- Add start date to Notes
-
Progress Updates:
- Check off subtasks as completed
- Add brief notes about progress
- Update any changed requirements
-
Completing a Task:
- Update Status to "Complete"
- Check off all subtasks
- Move to Completed Enhancements
- Add completion date
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 · 188 lines · 1,141 tokens per session scan A dc333867e173
task-tracking-basic is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It adds 1,141 tokens to every session, about $0.0046 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to task-tracking-basic, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
task-tracking-advanced
Advanced task tracking for Level 4 Complex System tasks.
task-tracking-basic
Basic task tracking for Level 2 Simple Enhancement tasks.
task-tracking-intermediate
Cursor rule "task-tracking-intermediate" from alkoleft/mcp-bsl-platform-context, covering level 3 intermediate task tracking, 🔍 task tracking workflow, 📋 task entry template, requirements and components affected.
1c-coding-standards
Coding standards for BSL, the programming language used by the 1C business software platform. They cover naming, method documentation, database queries, collections, client-server code, and performance practices.
1c-skd-two-pass-preprocessing
A two-pass method for changing 1C report output before detailed records are combined into grouped totals. 1C's report system, СКД, builds reports by grouping and summarizing data.
testing-patterns
A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.