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.
git clone --depth 1 https://github.com/sudhasubash1990/Salesforce-Enterprise-skillsWrote 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/userstory-generation)<a href="https://agentmods.dev/rules/sudhasubash1990/salesforce-enterprise-skills/userstory-generation"><img src="https://agentmods.dev/badge/rules/sudhasubash1990/salesforce-enterprise-skills/userstory-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/userstory-generation"><img src="https://agentmods.dev/badge/rules/sudhasubash1990/salesforce-enterprise-skills/userstory-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.02662 | $0.02662 |
| Opus 5 | $0.01331 | $0.01331 |
| Sonnet 5 | $0.00532 | $0.00532 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
userstory-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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Generate complete and production-ready Azure DevOps (ADO) User Stories following Agile best practices and the Salesforce BA skill pack.
Mandatory reads before generating:
Brain modules (per loading order — do NOT skip):
- salesforce-business-analyst/brain/identity.md — BA role and scope
- salesforce-business-analyst/brain/consulting-principles.md — enterprise behaviour
- salesforce-business-analyst/brain/reasoning-framework.md — 13-stage reasoning
- salesforce-business-analyst/brain/output-framework.md — artifact selection (required for deliverable generation)
- salesforce-business-analyst/brain/decision-framework.md — if fit-gap classification is produced
- salesforce-business-analyst/brain/validation-framework.md — pre-delivery validation
- salesforce-business-analyst/brain/anti-hallucination.md — estimation red flags
Knowledge and templates:
- salesforce-business-analyst/skill.md — Step 5 User Stories + Pre-Execution Gate
- salesforce-business-analyst/knowledge/user-stories.md
- salesforce-business-analyst/knowledge/acceptance-criteria.md
- salesforce-business-analyst/knowledge/ado-backlog-integration.md
- salesforce-business-analyst/templates/user-story-template.md
Salesforce Cloud knowledge (load when specific cloud is referenced):
- salesforce-business-analyst/knowledge/salesforce-clouds-overview.md
- salesforce-business-analyst/knowledge/service-cloud-patterns.md — if Service Cloud
- salesforce-business-analyst/knowledge/security-model.md — if permission/CRUD analysis needed
The generated user story must be ready for:
- Sprint Planning
- Backlog Refinement
- Development
- QA Test Case Design
- UAT Execution
Do not generate Apex/LWC implementation details unless explicitly requested.
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.
- 11d ago First seen · 364 lines · 2,662 tokens per session scan A ae4d35bd453d
userstory-generation is a cursor rule published in the GitHub repository sudhasubash1990/Salesforce-Enterprise-skills (3 stars, last pushed 23d ago), licensed MIT. It adds 2,662 tokens to every session, about $0.0133 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.