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 yu-iskw/skill-inspector --skill clean-projectgit clone --depth 1 https://github.com/yu-iskw/skill-inspectorWrote 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/yu-iskw/skill-inspector/clean-project)<a href="https://agentmods.dev/skills/yu-iskw/skill-inspector/clean-project"><img src="https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/clean-project.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.1 | $0.00042 | $0.00382 |
| Opus 5 | $0.00021 | $0.00191 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade C, and why
clean-project 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 8d 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.
- Recursively delete `node_modules`: `find . -name "node_modules" -type d -prune -exec rm -rf '{}' +`. Copies of this mod
1 near-identical copy found in the catalogue:
- clean-project — 100% identical, 0 lines differ
What it actually says
Clean Project (Hard Reset)
This skill provides a destructive but thorough way to repair a "broken" development environment by removing all cached artifacts and re-initializing from scratch.
When to Use
pnpm installfails repeatedly with checksum or resolution errors.trunkreports internal errors that persist aftertrunk install.- "Ghost" errors occur (failures that don't match the current code).
Workflow
-
Clean Dependencies:
- Recursively delete
node_modules:find . -name "node_modules" -type d -prune -exec rm -rf '{}' +. - Remove global lockfile:
rm pnpm-lock.yaml.
- Recursively delete
-
Clean Tooling Cache:
- Clear Trunk cache:
trunk clean. - Prune pnpm store:
pnpm store prune.
- Clear Trunk cache:
-
Re-initialize Environment:
- Invoke the
setup-dev-envskill to reinstall everything.
- Invoke the
-
Verify Health:
- Invoke the
verifiersubagent (../../agents/verifier.md) to ensure the project is back to a clean, working state.
- Invoke the
Safety Note
This process is destructive to the local environment but safe for the repository. It will require a full download of all dependencies, which may take several minutes depending on network speed.
Resources
- pnpm Commands for Node.js: Common pnpm maintenance commands.
- Trunk CLI Reference: Commands for managing Trunk artifacts.
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.
- 8d ago First seen · 40 lines · 42 tokens per session scan C 6a99a28527ad
clean-project is a skill published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 42 tokens to every session and 382 once invoked, about $0.0002 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-31.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.