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.
git clone --depth 1 https://github.com/sudhasubash1990/Salesforce-Enterprise-skillsnpx agentmods add rules/sudhasubash1990/salesforce-enterprise-skills/output-generationWrote 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.
[](https://agentmods.dev/rules/sudhasubash1990/salesforce-enterprise-skills/output-generation)<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.
<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>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.
| Model | Per session | Once 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 |
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.
What it actually says
Output Generation Rules
Whenever an artifact is generated:
-
Save the primary artifact as Markdown.
-
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 |
-
Routing uses generic rules in
output-engine/configuration/routing_rules.json(bydocument_typeand filename patterns). Optional project override:outputs/<project>/format-routing.json. -
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
-
Preserve folder hierarchy.
-
Do not overwrite existing converted files unless
output-engine/output-config.jsonsets"overwrite": trueor the CLI passes--overwrite. -
Log every conversion in
conversion_report.jsonat 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
.docxand fallback.pdf) -
Python packages: see
output-engine/requirements.txt -
Microsoft Word (recommended on Windows for
.pdfgeneration viadocx2pdf)
See output-engine/README.md for architecture and extension guide.
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.
- 12d ago First seen · 125 lines · 467 tokens per session scan A bd31c4a7cc27
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.
Other cursor rules, from other repositories
shard-doc
BMAD CORE Tool: Shard Document.
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, invoices, statements, regulatory documents, and PDF delivery. Covers report pages, absolute pixel layout, header/footer panels, common elements, verification…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.