output-generation

output-generation is a cursor rule for Cursor from sudhasubash1990/Salesforce-Enterprise-skills. It costs 467 tokens per session, scanned A, original, MIT.

A set of rules for turning generated Markdown documents into a suitable office file, such as a Word document, presentation, spreadsheet, or PDF.

In plain words
What is it for?
It helps create readable deliverables from narratives, slide outlines, registers, checklists, requirements documents, and similar project artifacts.
Why use it?
It removes the need to choose output formats and convert files manually while keeping converted files beside their Markdown sources.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python output-engine/convert.py --file "outputs/<project-folder>/path/to/artifact.md".

Good fit It helps create readable deliverables from narratives, slide outlines, registers, checklists, requirements documents, and similar project artifacts.

Compare 6 cursor rules from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/sudhasubash1990/Salesforce-Enterprise-skills
agentmods
npx agentmods add rules/sudhasubash1990/salesforce-enterprise-skills/output-generation

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 output-generation

README.md
[![agentmods](https://agentmods.dev/badge/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation/github.svg)](https://agentmods.dev/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation)
Your own site
<a href="https://agentmods.dev/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation"><img src="https://agentmods.dev/badge/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation/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 output-generation

Your own site · 80×15
<a href="https://agentmods.dev/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation"><img src="https://agentmods.dev/badge/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 467 This file is loaded in full into every session.
When invoked 467 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 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.00467 $0.00467
Opus 5 $0.00234 $0.00234
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

output-generation 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 12d 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/output-generation.mdc · 125 lines

What it actually says

Output Generation Rules

Whenever an artifact is generated:

  1. Save the primary artifact as Markdown.

  2. Run intelligent conversion to one user-readable office format per file:

| Format | Use when |

|--------|----------|

| .docx | Narrative documents, workshops, analysis, process maps, plans |

| .pptx | Slide-deck / presentation outlines (## Slide N or H1/H2 structure) |

| .xlsx | Registers, matrices, checklists, backlogs, user stories, test scenarios |

| .pdf | Formal requirements baselines (BRD, FRD, NFR) for sign-off distribution |

  1. Routing uses generic rules in output-engine/configuration/routing_rules.json (by document_type and filename patterns). Optional project override: outputs/<project>/format-routing.json.

  2. Save the converted file beside the Markdown source (same folder).

Example:


03-requirements/

  brd.md

  brd.pdf

  user-stories/

    epic-01-onboarding-stories.md

    epic-01-onboarding-stories.xlsx

08-executive/

  steering-committee-presentation.md

  steering-committee-presentation.pptx

  1. Preserve folder hierarchy.

  2. Do not overwrite existing converted files unless output-engine/output-config.json sets "overwrite": true or the CLI passes --overwrite.

  3. Log every conversion in conversion_report.json at the project output root.

Conversion commands

Single file (after each write):


python output-engine/convert.py --file "outputs/<project-folder>/path/to/artifact.md"

Full project batch:


python output-engine/convert.py --root "outputs/<project-folder>" --overwrite

Prerequisites

  • Pandoc (for .docx and fallback .pdf)

  • Python packages: see output-engine/requirements.txt

  • Microsoft Word (recommended on Windows for .pdf generation via docx2pdf)

See output-engine/README.md for architecture and extension guide.

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. 12d ago First seen · 125 lines · 467 tokens per session scan A bd31c4a7cc27

Subscribe to this mod's changes

output-generation is a cursor rule published in the GitHub repository sudhasubash1990/Salesforce-Enterprise-skills (3 stars, last pushed 23d ago), licensed MIT. It adds 467 tokens to every session, about $0.0023 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.