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/rweisssieker-xp/GBL-CREO-WINDCHILL-MCPWrote 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/rweisssieker-xp/gbl-creo-windchill-mcp/create-story)<a href="https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-story"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-story/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/rweisssieker-xp/gbl-creo-windchill-mcp/create-story"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-story.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.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
create-story 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: create-story description: "Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking" author: "BMad"
Critical variables from config
config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" story_dir: "{sprint_artifacts}"
Workflow components
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.xml" validation: "{installed_path}/checklist.md"
Variables and inputs
variables: sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking epics_file: "{output_folder}/epics.md" # Enhanced epics+stories with BDD and source hints prd_file: "{output_folder}/PRD.md" # Fallback for requirements (if not in epics file) architecture_file: "{output_folder}/architecture.md" # Fallback for constraints (if not in epics file) ux_file: "{output_folder}/ux.md" # Fallback for UX requirements (if not in epics file) story_title: "" # Will be elicited if not derivable
Project context
project_context: "**/project-context.md"
default_output_file: "{story_dir}/{{story_key}}.md"
Smart input file references - Simplified for enhanced approach
The epics+stories file should contain everything needed with source hints
input_file_patterns: prd: description: "PRD (fallback - epics file should have most content)" whole: "{output_folder}/prd.md" sharded: "{output_folder}/prd/.md" load_strategy: "SELECTIVE_LOAD" # Only load if needed architecture: description: "Architecture (fallback - epics file should have relevant sections)" whole: "{output_folder}/architecture.md" sharded: "{output_folder}/architecture/.md" load_strategy: "SELECTIVE_LOAD" # Only load if needed ux: description: "UX design (fallback - epics file should have relevant sections)" whole: "{output_folder}/ux.md" sharded: "{output_folder}/ux/.md" load_strategy: "SELECTIVE_LOAD" # Only load if needed epics: description: "Enhanced epics+stories file with BDD and source hints" whole: "{output_folder}/epic.md" sharded: "{output_folder}/epic/.md" load_strategy: "SELECTIVE_LOAD" # Only load needed epic
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 · 65 lines · 654 tokens per session scan A 1a9ea4e09619
create-story is a cursor rule published in the GitHub repository rweisssieker-xp/GBL-CREO-WINDCHILL-MCP (4 stars, last pushed 9mo ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 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.