07-deploy-after-changes

07-deploy-after-changes is a cursor rule for Cursor from Brano80/Veridion-nexus. It costs 457 tokens per session, scanned A, original, no licence file.

A Cursor rule that tells the agent how and when to deploy code after changes. It covers a marketing website, a backend, what counts as a substantial change, and the order for deploying both.

In plain words
What is it for?
Use it in the Veridion-nexus project to guide deployments after backend or marketing-site changes, unless deployment is explicitly skipped.
Why use it?
It makes the deployment step part of the expected workflow instead of leaving it to memory. This can reduce the chance that completed code changes are not published.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it in the Veridion-nexus project to guide deployments after backend or marketing-site changes, unless deployment is explicitly skipped.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/brano80/veridion-nexus/07-deploy-after-changes
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Brano80/Veridion-nexus

Made for: Cursor.

Wrote 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.

agentmods badge for 07-deploy-after-changes

README.md
[![agentmods](https://agentmods.dev/badge/rules/brano80/veridion-nexus/07-deploy-after-changes/github.svg)](https://agentmods.dev/rules/brano80/veridion-nexus/07-deploy-after-changes)
Your own site
<a href="https://agentmods.dev/rules/brano80/veridion-nexus/07-deploy-after-changes"><img src="https://agentmods.dev/badge/rules/brano80/veridion-nexus/07-deploy-after-changes/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.

agentmods 80×15 button for 07-deploy-after-changes

Your own site · 80×15
<a href="https://agentmods.dev/rules/brano80/veridion-nexus/07-deploy-after-changes"><img src="https://agentmods.dev/badge/rules/brano80/veridion-nexus/07-deploy-after-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 457 This file is loaded in full into every session.
When invoked 457 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00457 $0.00457
Opus 5.5 $0.00183 $0.00183
Sonnet 5.5 $0.00091 $0.00091
Haiku 4.5 $0.00046 $0.00046

Measured 2mo ago against content hash 8e2caeca96e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

07-deploy-after-changes 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 2mo 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.

.cursor/rules/07-deploy-after-changes.mdc · 45 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 2mo ago First seen · 45 lines · 457 tokens per session scan A 8e2caeca96e8

Subscribe to this mod's changes

07-deploy-after-changes is a cursor rule published in the GitHub repository Brano80/Veridion-nexus (0 stars, last pushed 5mo ago), with no licence file. It adds 457 tokens to every session, about $0.0018 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-31.