code-output-rules

code-output-rules is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (110 once invoked), scanned A, original, MIT.

Code-output guidelines that require complete, usable file contents with imports, declarations, surrounding code, and comments for important changes.

In plain words
What is it for?
Use them when an agent generates or edits source files and needs to show code that can be used directly.
Why use it?
They reduce the chance that copied code is missing something needed to run or is difficult to place in the project.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use them when an agent generates or edits source files and needs to show code that can be used directly.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/code-output-rules
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/holtwood/awesome-cursorrules-zh

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 code-output-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/code-output-rules/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/code-output-rules)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/code-output-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/code-output-rules/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 code-output-rules

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/code-output-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/code-output-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 110 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00110
Opus 5 $0.00000 $0.00055
Sonnet 5 $0.00000 $0.00022
Haiku 4.5 $0.00000 $0.00011

Measured 6d ago against content hash 665baca92a79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

code-output-rules 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 6d 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.

docs/rules/frontend/chrome/chrome-extension-dev-js-typescript/code-output-rules.mdc · 9 lines

What it actually says

  • 提供代码时,始终输出完整文件内容,而不仅是新增或修改部分
  • 包含所有必要的导入、声明和周边代码以确保文件完整可用
  • 对重要变更或新增内容提供注释说明
  • 如文件过大,提供最相关的完整部分并说明其在文件结构中的位置
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. 6d ago First seen · 9 lines · 110 tokens per session scan A 665baca92a79

Subscribe to this mod's changes

code-output-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 110 tokens. 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-09-03.