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/retrospective)<a href="https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/retrospective"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/retrospective/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/retrospective"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/retrospective.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.00007 | $0.00577 |
| Opus 5.5 | $0.00003 | $0.00231 |
| Sonnet 5.5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
retrospective 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 1mo 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.
This is a copy
89% identical to correct-course — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective - Epic Completion Review Workflow
name: "retrospective" description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic" author: "BMad"
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" user_skill_level: "{config_source}:user_skill_level" document_output_language: "{config_source}:document_output_language" date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts"
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective" template: false instructions: "{installed_path}/instructions.md"
required_inputs:
- agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv"
Smart input file references - handles both whole docs and sharded docs
Priority: Whole document first, then sharded version
Strategy: SELECTIVE LOAD - only load the completed epic and relevant retrospectives
input_file_patterns: epics: description: "The completed epic for retrospective" whole: "{output_folder}/epic.md" sharded_index: "{output_folder}/epic/index.md" sharded_single: "{output_folder}/epic/epic-{{epic_num}}.md" load_strategy: "SELECTIVE_LOAD" previous_retrospective: description: "Previous epic's retrospective (optional)" pattern: "{sprint_artifacts}/**/epic-{{prev_epic_num}}-retro-.md" load_strategy: "SELECTIVE_LOAD" architecture: description: "System architecture for context" whole: "{output_folder}/architecture.md" sharded: "{output_folder}/architecture/.md" load_strategy: "FULL_LOAD" prd: description: "Product requirements for context" whole: "{output_folder}/prd.md" sharded: "{output_folder}/prd/.md" load_strategy: "FULL_LOAD" document_project: description: "Brownfield project documentation (optional)" sharded: "{output_folder}/.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.
- 1mo ago First seen · 62 lines · 577 tokens per session scan A 20b228dfc9f6
retrospective is a cursor rule published in the GitHub repository rweisssieker-xp/GBL-CREO-WINDCHILL-MCP (4 stars, last pushed 10mo ago), licensed MIT. It adds 7 tokens to every session and 577 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to correct-course, differing in 63 lines, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.