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/reportsgit 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.01099 |
| Opus 5 | $0.00000 | $0.00549 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
reports 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.
This is a copy
100% identical to reports — 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VAN QA: VALIDATION REPORTS
TL;DR: This component contains the formats for comprehensive success and failure reports generated upon completion of the QA validation process.
📋 COMPREHENSIVE SUCCESS REPORT FORMAT
After all four validation points pass, generate this success report:
╔═════════════════════ 🔍 QA VALIDATION REPORT ══════════════════════╗
│ PROJECT: [Project Name] | TIMESTAMP: [Current Date/Time] │
├─────────────────────────────────────────────────────────────────────┤
│ 1️⃣ DEPENDENCIES: ✓ Compatible │
│ 2️⃣ CONFIGURATION: ✓ Valid & Compatible │
│ 3️⃣ ENVIRONMENT: ✓ Ready │
│ 4️⃣ MINIMAL BUILD: ✓ Successful & Passed │
├─────────────────────────────────────────────────────────────────────┤
│ 🚨 FINAL VERDICT: PASS │
│ ➡️ Clear to proceed to BUILD mode │
╚═════════════════════════════════════════════════════════════════════╝
Success Report Generation Example:
function Generate-SuccessReport {
param (
[string]$ProjectName = "Current Project"
)
$timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
$report = @"
╔═════════════════════ 🔍 QA VALIDATION REPORT ══════════════════════╗
│ PROJECT: $ProjectName | TIMESTAMP: $timestamp │
├─────────────────────────────────────────────────────────────────────┤
│ 1️⃣ DEPENDENCIES: ✓ Compatible │
│ 2️⃣ CONFIGURATION: ✓ Valid & Compatible │
│ 3️⃣ ENVIRONMENT: ✓ Ready │
│ 4️⃣ MINIMAL BUILD: ✓ Successful & Passed │
├─────────────────────────────────────────────────────────────────────┤
│ 🚨 FINAL VERDICT: PASS │
│ ➡️ Clear to proceed to BUILD mode │
╚═════════════════════════════════════════════════════════════════════╝
"@
# Save validation status (used by BUILD mode prevention mechanism)
"PASS" | Set-Content -Path "memory-bank\.qa_validation_status"
return $report
}
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 · 149 lines · 0 tokens per session scan A fce1d58f59ba
reports is a cursor rule published in the GitHub repository alkoleft/mcp-bsl-platform-context (191 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,099 tokens. A static security scan graded it A with 0 findings. It is 100% identical to reports, differing in 0 lines, and is treated as a copy.
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С (СКД) без схемы компоновки.
1c-transactions-and-locks
Транзакции и управляемые блокировки: шаблон, порядок захвата.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).