engineering-standards

engineering-standards is a cursor rule for Cursor from hlalljie/agent-workflow-presets. It costs 145 tokens per session, scanned A, original, MIT.

A set of engineering rules covering security defaults, planning choices, and thinking about failures before implementation.

In plain words
What is it for?
It is for planning with alternatives, securing production code, assessing failure and rollback paths, and considering cost before recommending an approach.
Why use it?
It helps avoid exposed secrets, overly broad access, unexamined trade-offs, and fixes that are difficult to undo.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/hlalljie/agent-workflow-presets/engineering-standards
Clone the repo
git clone --depth 1 https://github.com/hlalljie/agent-workflow-presets

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 engineering-standards

README.md
[![agentmods](https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/engineering-standards.svg)](https://agentmods.dev/rules/hlalljie/agent-workflow-presets/engineering-standards)
Your own site
<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/engineering-standards"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/engineering-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 145 This file is loaded in full into every session.
When invoked 145 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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 $0.00145 $0.00145
Opus 5 $0.00072 $0.00072
Sonnet 5 $0.00029 $0.00029
Haiku 4.5 $0.00015 $0.00015

Measured 3d ago against content hash b66637852fd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

engineering-standards 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 3d 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/engineering-standards.mdc · 16 lines

What it actually says

When planning or discussing: present viable options with trade-offs. Don't collapse to one answer when multiple good approaches exist.

When implementing: apply the right approach for context. If user wants something exploratory or throwaway, confirm trade-offs and proceed.

Security defaults for committed/production code:

  • Secrets in env vars or secret manager, never in code or CLI args
  • Authenticated endpoints by default
  • Least-privilege access

Think through failure modes, rollback, and cost before suggesting. If a previous suggestion was wrong, say so and correct it. If something creates future problems, flag it.

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. 3d ago First seen · 16 lines · 145 tokens per session scan A b66637852fd1

Subscribe to this mod's changes

engineering-standards is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session, about $0.0007 per session on Opus 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.