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/implementation-readiness)<a href="https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/implementation-readiness"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/implementation-readiness/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/implementation-readiness"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/implementation-readiness.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.00009 | $0.00642 |
| Opus 5 | $0.00005 | $0.00321 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
implementation-readiness 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Readiness - Workflow Configuration
name: implementation-readiness description: "Validate that PRD, UX Design, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation. Ensures all artifacts cover the MVP requirements with no gaps or contradictions." 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" document_output_language: "{config_source}:document_output_language" date: system-generated
Workflow status integration
workflow_status_workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml" workflow_paths_dir: "{project-root}/.bmad/bmm/workflows/workflow-status/paths" workflow_status_file: "{output_folder}/bmm-workflow-status.yaml"
Module path and component files
installed_path: "{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md"
Output configuration
default_output_file: "{output_folder}/implementation-readiness-report-{{date}}.md"
Smart input file references - handles both whole docs and sharded docs
Priority: Whole document first, then sharded version
Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
input_file_patterns: prd: description: "Product Requirements with FRs and NFRs" whole: "{output_folder}/prd.md" sharded: "{output_folder}/prd/index.md" load_strategy: "FULL_LOAD" epics: description: "Epic breakdown with user stories" whole: "{output_folder}/epic.md" sharded: "{output_folder}/epic/index.md" load_strategy: "FULL_LOAD" architecture: description: "System architecture with decisions and patterns" whole: "{output_folder}/architecture.md" sharded: "{output_folder}/architecture/index.md" load_strategy: "FULL_LOAD" ux_design: description: "UX design specification (if UI components)" whole: "{output_folder}/ux.md" sharded: "{output_folder}/ux/index.md" load_strategy: "FULL_LOAD" tech_spec: description: "Technical specification (for Quick Flow track)" whole: "{output_folder}/tech-spec.md" sharded: "{output_folder}/tech-spec/index.md" load_strategy: "FULL_LOAD" document_project: description: "Brownfield project documentation (optional)" sharded: "{output_folder}/index.md" load_strategy: "INDEX_GUIDED"
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.
- 6d ago First seen · 69 lines · 642 tokens per session scan A 700b8b94f999
implementation-readiness 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 9 tokens to every session and 642 once invoked, about $0.0000 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-09-03.
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.