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/alkoleft/mcp-bsl-platform-context/task-tracking-basicgit clone --depth 1 https://github.com/alkoleft/mcp-bsl-platform-contextWhat 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.00000 | $0.01141 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- task-tracking-basic — 100% identical, 0 lines differ
- task-tracking-basic — 100% identical, 0 lines differ
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.
- 2d 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/mcp-bsl-platform-context (190 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,141 tokens. 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
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).
designer-batch-verdict
Вердикт пакетного запуска платформы: четыре сигнала вместо кода возврата.