Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/whitequeen306/code-cortex-loopnpx agentmods add rules/whitequeen306/code-cortex-loop/baseline-policyWrote 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/whitequeen306/code-cortex-loop/baseline-policy)<a href="https://agentmods.dev/rules/whitequeen306/code-cortex-loop/baseline-policy"><img src="https://agentmods.dev/badge/rules/whitequeen306/code-cortex-loop/baseline-policy/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/whitequeen306/code-cortex-loop/baseline-policy"><img src="https://agentmods.dev/badge/rules/whitequeen306/code-cortex-loop/baseline-policy.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.00015 | $0.00439 |
| Opus 5.5 | $0.00006 | $0.00176 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
baseline-policy 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.
What it actually says
Baseline Policy (CodeCortexLoop v2.1)
Purpose
Legacy codebases may have hundreds of pre-existing findings. Baseline mode lets teams adopt CodeCortexLoop without blocking every PR on old debt.
Fingerprint
Each finding gets a stable fingerprint:
hash(category + location_with_line + full_normalized_problem)
- Location includes line numbers (file paths normalized to forward slashes)
- Problem normalized: lowercase, whitespace collapsed, full text (not truncated)
Same issue at same place = same fingerprint across runs.
Buckets
| Bucket | Definition |
|---|---|
| new | In current report, not in baseline |
| fixed | In baseline, not in current open findings |
| remaining | In both — accepted technical debt |
Accept baseline
Run once (or when intentionally accepting new debt):
node scripts/baseline.mjs accept docs/cortexloop/report.json
Stores .cortexloop/baseline.json. Commit this file to the repo so CI shares the same baseline.
Diff
Every PR / run after baseline exists:
node scripts/baseline.mjs diff docs/cortexloop/report.json
Produces .cortexloop/baseline-diff.json.
CI gate with --baseline
node scripts/ci-gate.mjs docs/cortexloop/report.json --baseline
Counts only new findings for Critical/High exit codes. Remaining baseline debt does not fail CI.
When to re-accept
- Team deliberately accepts additional debt (discuss in PR)
- Fingerprint churn from mass renames (rare — prefer fixing root cause)
- Major refactor changes finding locations en masse
Re-accept only with explicit user confirmation.
Agent behavior
- Never auto-accept baseline in Direct mode
- Present new/fixed/remaining counts in summary
- Highlight new Critical/High prominently
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 · 74 lines · 15 tokens per session scan A 4f84ba2826e4
baseline-policy is a cursor rule published in the GitHub repository whitequeen306/code-cortex-loop (15 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 439 once invoked, about $0.0001 per session on Opus 5.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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.