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 skills add gullitmiranda/.cursor --skill workspace-statusgit 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/workspace-status)<a href="https://agentmods.dev/skills/gullitmiranda/.cursor/workspace-status"><img src="https://agentmods.dev/badge/skills/gullitmiranda/.cursor/workspace-status/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/skills/gullitmiranda/.cursor/workspace-status"><img src="https://agentmods.dev/badge/skills/gullitmiranda/.cursor/workspace-status.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.00034 | $0.00484 |
| Opus 5 | $0.00017 | $0.00242 |
| Sonnet 5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
workspace-status 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Status Command
Description
Multi-repository workspace status overview with comprehensive analysis.
Workflow
- 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
- Identify which specific repository changes belong to
- Navigate to correct repository directory before running git operations
- Treat each repository as separate entity with its own git state
Multi-Repository Handling
- When working with staged changes, identify which specific repository they belong to
- Provide clear indication of repository boundaries
- Show status for each repository found in workspace
- Highlight any cross-repository dependencies or conflicts
Error Prevention
- Always ask for clarification when workspace structure is unclear
- Confirm target repository before running git commands
- Use non-destructive git commands first (git stash, git log) to understand situation
Output Format
Workspace: /path/to/workspace
Repositories: 3
Repository 1: /path/to/repo1
Branch: main
Status: clean
Last commit: 2 hours ago
Remote: origin/main
Repository 2: /path/to/repo2
Branch: feature/new-feature
Status: dirty
Staged: 2 files
Modified: 1 file
Last commit: 1 hour ago
Remote: origin/feature/new-feature
Repository 3: /path/to/repo3
Branch: develop
Status: clean
Last commit: 3 hours ago
Remote: origin/develop
Examples
# Check workspace status
/workspace-status
# Check specific workspace
/workspace-status /path/to/workspace
# Detailed status with file changes
/workspace-status --detailed
Features
- Multi-repository detection
- Cross-repository dependency analysis
- Conflict detection and reporting
- Workspace boundary identification
- Git state analysis per repository
Integration
- Works with all git commands
- Integrates with PR workflow
- Supports Linear issue tracking
- Compatible with branch management
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 · 87 lines · 34 tokens per session scan A 30246ae0d9ab
workspace-status is a skill published in the GitHub repository gullitmiranda/.cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 484 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.