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/JosiahSiegel/claude-plugin-marketplaceWrote 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/commands/josiahsiegel/claude-plugin-marketplace/pwsh-script)<a href="https://agentmods.dev/commands/josiahsiegel/claude-plugin-marketplace/pwsh-script"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/pwsh-script/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/commands/josiahsiegel/claude-plugin-marketplace/pwsh-script"><img src="https://agentmods.dev/badge/commands/josiahsiegel/claude-plugin-marketplace/pwsh-script.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.00024 | $0.01128 |
| Opus 5 | $0.00012 | $0.00564 |
| Sonnet 5 | $0.00005 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade C, and why
pwsh-script scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
[[ -n "${TEMP_DIR:-}" ]] && rm -rf "$TEMP_DIR" How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 CRITICAL GUIDELINES
Windows File Path Requirements
MANDATORY: Always Use Backslashes on Windows for File Paths
When using Edit or Write tools on Windows, you MUST use backslashes (\) in file paths, NOT forward slashes (/).
Examples:
- ❌ WRONG:
D:/repos/project/file.tsx - ✅ CORRECT:
D:\repos\project\file.tsx
This applies to:
- Edit tool file_path parameter
- Write tool file_path parameter
- All file operations on Windows systems
Documentation Guidelines
NEVER create new documentation files unless explicitly requested by the user.
- Priority: Update existing README.md files rather than creating new documentation
- Repository cleanliness: Keep repository root clean - only README.md unless user requests otherwise
- Style: Documentation should be concise, direct, and professional - avoid AI-generated tone
- User preference: Only create additional .md files when user specifically asks for documentation
Create/Review Bash Scripts
Purpose
Autonomously create professional, production-ready bash scripts or review/optimize existing scripts following 2025 industry standards.
What This Command Does
Automatic Actions:
- ✅ Creates scripts with mandatory error handling (set -euo pipefail)
- ✅ Implements ShellCheck-compliant code
- ✅ Follows Google Shell Style Guide (50-line recommendation)
- ✅ Adds comprehensive error handling and cleanup
- ✅ Ensures cross-platform compatibility
- ✅ Includes proper documentation
- ✅ Validates security patterns
For Reviews:
- Identifies ShellCheck issues
- Checks for security vulnerabilities
- Validates error handling
- Suggests performance optimizations
- Verifies cross-platform compatibility
Usage
Create a new script:
/pwsh-script Create a backup script that archives /data to S3 with error handling
Review existing script:
/pwsh-script Review backup.sh for security issues and best practices
Optimize performance:
/pwsh-script Optimize deploy.sh for better performance
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.
- 11d ago First seen · 176 lines · 24 tokens per session scan C d6fac3b51c80
pwsh-script is a command published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (54 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 1,128 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.