Official recipe

Detect regression in repository security rules

Cross-file changes can weaken agreed security rules.

Read original recipe

Proposed inputs

Name
Rule list
Owner
Security owner
Minimum scope
Explicit repository rules
Quality check
Name scope and exceptions.
Name
Versioned code evidence
Owner
Maintainer
Minimum scope
Two permitted revisions
Quality check
Pin commits and locations.
Name
Prior status ledger
Owner
Reviewer
Minimum scope
Reviewed prior evidence
Quality check
Missing history is unknown.

Access and setup — proposed or unknown

Proposed minimum: Begin with supplied fictional code excerpts and a read-only comparison.
Keep alert delivery, executable probes and persistent automation disabled for the first review.
Compatibility unknowns: Unknown: repository coverage, execution sandbox and memory integrity.
Unknown: branch selection, generated code visibility and integration permissions.
External actions requiring approval: Running repository code, persisting a monitor, connecting private sources or sending security findings to Slack.

Detailed steps and output format

At a glance

Suggested result: Rule ledger and code-linked change report.Suggested; untested.
Tool: Cursor AutomationsSource-named; check current access.
Suggested inputs: Rule list; Versioned code evidence; Prior status ledgerProposed; access notes below.
Human review: Approve scope, data access, spending and installed integrations separately. Require owner acceptance and a recovery decision before connecting real systems, sending anything or…
Read full note
Approve scope, data access, spending and installed integrations separately. Require owner acceptance and a recovery decision before connecting real systems, sending anything or deploying.
Suggested boundaries; source approvals below.
Setup notes: Begin with supplied fictional code excerpts and a read-only comparison. Keep alert delivery, executable probes and persistent automation disabled for the first review.Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Function and scope

IT & security, Software engineering · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Cross-file changes can weaken agreed security rules.

Suggested task · untested

Proposed: corroborate repository-rule changes against prior evidence.

What you could produce

Rule ledger and code-linked change report.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Proposed guidance and fictional tests; source-shaped procedures remain attributed to the linked original. No execution is claimed.

Read the attributed source evidence and original caveats below ↓

Why use this

Enforcement may span several code paths.
Prior-state comparison focuses review on changes.

Why an agent / simpler alternative

Useful judgment: Trace cross-file enforcement and uncertainty.
Simpler alternative: Use deterministic policy tests when the rule has a reliable executable oracle.
Unsuitable when: The repository is unauthorized, the baseline is untrusted or the rule is too vague to assess.

Expected deliverable and review checks

Proposed artifact: Rule ledger and code-linked change report.
Critical checks: Corroborate regressions; retain unknowns; alert only on changes.
Missing output evidence: Unknown: no runtime comparison, persisted baseline or delivered alert was independently verified.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Fictional rule R1 requires an owner check before deleting a draft. Revision A calls require_owner before delete_draft. Revision B routes a background cleanup directly to delete_draft; the definition of a second permission helper is unavailable.
Acceptance checks: Cite both bypass locations; missing helper stays inconclusive.
Do not claim full-repository security or update a live baseline.
Prepare a comparison ledger only; execute no code and send no alert.
Stop conditions: Code ownership or authorization is unclear.
A finding would expose secrets or require an unapproved executable probe.

Tasks: Build & debug Security & compliance Research & discovery

Useful for: Software developer

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Cursor AutomationsIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Helper unavailable.
Why it matters
Enforcement is unverified.
Proposed response
Hold inconclusive; request definition.
Signal
Unverified baseline replacement.
Why it matters
Errors become comparison truth.
Proposed response
Retain prior evidence pending review.

Effort and cost — unknown

Setup work: Approve rules and baseline.
Ongoing review: Review changes and unknowns.
Unknowns: Unknown: indexing, model calls, review effort and alert maintenance.

Limits

This proposed inspection supplements security review. It does not establish exhaustive coverage, absence of vulnerabilities or regulatory compliance.

Full source evidence

Official recipe · Tool workflows

Original task title: Detect regression in repository security rules

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://cursor.com/marketplace/automations/monitor-engineering-invariants ↗

Attributed to: Cursor

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.

security agents

Official recipe

Original action type: tool_action
What the source reports: The recipe corroborates invariant drift, stores enforced/drifted/inconclusive states and reports evidence-linked changes.
Source outcome limits: Unexecuted recipe. Repository coverage, memory baseline, runtime version, Slack access and permissions are unverified. An inconclusive result is not a clean security assessment; no compliance certification follows.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: Replace default invariants before enabling; no per-alert approval gate is specified.
Named tools: Cursor; repository; memory; Slack
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: review hosting region, handling of operational data, accessibility and local organizational requirements before any Canadian pilot. No Canadian execution or workflow availability was established.
Recommended approval boundaries: Approve scope, data access, spending and installed integrations separately. Require owner acceptance and a recovery decision before connecting real systems, sending anything or deploying.