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/toyamarinyon/giselleWrote 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/toyamarinyon/giselle/edit-workspace-tour)<a href="https://agentmods.dev/rules/toyamarinyon/giselle/edit-workspace-tour"><img src="https://agentmods.dev/badge/rules/toyamarinyon/giselle/edit-workspace-tour/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/toyamarinyon/giselle/edit-workspace-tour"><img src="https://agentmods.dev/badge/rules/toyamarinyon/giselle/edit-workspace-tour.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.00000 | $0.01303 |
| Opus 5 | $0.00000 | $0.00651 |
| Sonnet 5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
edit-workspace-tour 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 9d 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
100% identical to edit-workspace-tour — 0 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide to Edit Workspace Tour
The workspace tour is a user onboarding experience that guides new users through the Giselle workspace interface. This guide will help you understand the structure and make modifications to the tour.
File Structure
The workspace tour is located in:
internal-packages/workflow-designer-ui/src/editor/workspace-tour/
It contains:
- index.ts - Exports components and types
- steps.ts - Defines the tour steps content
- workspace-tour.tsx - Main component implementation
assets/- Images and GIFs for tour steps
Key Components
-
TourStep Interface (in
workspace-tour.tsx)export type TourStep = { target?: string; // CSS selector for element to highlight title: string; content: string; placement?: "top" | "bottom" | "left" | "right"; }; -
Tour Steps (in
steps.ts)export const tourSteps: TourStep[] = [ { title: "Welcome to Giselle", content: "This platform helps you build and manage AI workflows easily.", placement: "bottom", }, // Additional steps... ]; -
Step Components (in
workspace-tour.tsx)TourStep1- Overview with 3 columnsTourStep2- Toolbar tutorial with arrowTourStep3- Large centered card with GIFTourStep4- Small centered card with GIFTourStep5- Card with arrow in top-right cornerTourStep6- Final step in bottom-left corner
-
Visual Components
TourCard- Reusable card componentNavigationFooter- Navigation controlsTourGlobalStyles- CSS animationsTourOverlay- Transparent clickable overlay
Making Changes
To Edit Tour Content
- Modify the
tourStepsarray insteps.tsto change text, target elements, or placement - Be careful with CSS selectors in the
targetproperty - these need to match elements in the UI
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.
- 9d ago First seen · 154 lines · 0 tokens per session scan A b0bbef0388a3
edit-workspace-tour is a cursor rule published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,303 tokens. A static security scan graded it A with 0 findings. It is 100% identical to edit-workspace-tour, differing in 0 lines, and is treated as a copy.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.