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.
npx agentmods add skills/gullitmiranda/.cursor/workflownpx skills add gullitmiranda/.cursor --skill workflowgit clone --depth 1 https://github.com/gullitmiranda/.cursorWrote 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/skills/gullitmiranda/.cursor/workflow)<a href="https://agentmods.dev/skills/gullitmiranda/.cursor/workflow"><img src="https://agentmods.dev/badge/skills/gullitmiranda/.cursor/workflow.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00589 |
| Opus 5 | $0.00021 | $0.00295 |
| Sonnet 5 | $0.00008 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
workflow 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Rules
Language
- By default always write documentation, comments, code, commit messages, and pull request titles/descriptions in English
- Use English for all technical communication including:
- Code comments and documentation
- Commit messages and commit descriptions
- Pull request titles and descriptions
- Technical documentation and README files
- API documentation and code examples
Integrated Terminal
- Prefer terminal commands over GUI operations when possible
Temporary Files Management
- When creating temporary files, use temporary directories (
./tmpor system tmp) - Never commit temporary files to version control
Workspace & Multi-Repository Rules
Workspace Structure Awareness
- Always check current working directory and understand repository boundaries
- Never assume single git repository when working in multi-repo workspace
- Always verify which repository operations are targeting before execution
Multi-Repository Handling
- When working with staged changes, identify which specific repository they belong to
- Navigate to correct repository directory before running git operations
- Treat each repository as separate entity with its own git state
Branch Management
- Create feature branches from main/master
- Use descriptive branch names
- Keep branches focused on single features
- Delete merged branches
Commit Workflow
- Only commit when explicitly requested
- Never commit unstaged changes without explicit request
- Never commit directly to main/master branch
- Make small, focused commits
- Use conventional commit format
- Include meaningful commit messages
- Reference Linear issues when applicable
PR Workflow
- Create PRs for all main branch changes
- Use descriptive PR titles
- Include comprehensive descriptions
- Request appropriate reviewers
Planning Workflow
Plan Creation Guidelines
- Create plans in
.cursor/plans/directory - Use clear, actionable task breakdown
- Include dependencies and prerequisites
- Format as markdown with clear sections
- NEVER include timelines or schedules
- NEVER generate cronograms or time estimates
- Focus on what needs to be done, not when
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.
- 4d ago First seen · 99 lines · 42 tokens per session scan A b24c94849538
workflow is a skill published in the GitHub repository gullitmiranda/.cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 589 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…