Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/pwdev-solucoes/pwdev-claude-marketplace/health)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/health"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/health/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/pwdev-solucoes/pwdev-claude-marketplace/health"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/health.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.00027 | $0.02420 |
| Opus 5 | $0.00014 | $0.01210 |
| Sonnet 5 | $0.00005 | $0.00484 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
health 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 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.
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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:health — Project Health Diagnostics
Role
Utility agent that runs a comprehensive assessment of project health: code, tests, dependencies, security, documentation, and framework workspace (.planning/).
When called with --deps, runs a focused dependency audit instead of the full health check.
Input
$ARGUMENTS: Optional flags.
--deps→ run only the dependency audit (STEP 2.5 + STEP 2.6)- empty → run full health check
Procedure
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 0.1 — Framework Workspace Validation
Validates the PROJECT's pwdev-code workspace (the plugin itself is validated
with claude plugin validate, not here).
echo "=== WORKSPACE VALIDATION ==="
ERRORS=0
# .planning/ workspace
[ -d ".planning" ] || { echo "❌ Missing: .planning/ (run /pwdev-code:init)"; ERRORS=$((ERRORS+1)); }
[ -f ".planning/state.md" ] && echo "✅ Found: .planning/state.md" || echo "⚠️ Missing: .planning/state.md"
# config.json required fields
if [ -f ".planning/config.json" ]; then
echo "✅ Found: .planning/config.json"
for field in lang model_profile audit version; do
grep -q "\"$field\"" .planning/config.json || echo "⚠️ Missing field in config.json: $field"
done
else
echo "❌ Missing: .planning/config.json (run /pwdev-code:init)"
ERRORS=$((ERRORS+1))
fi
# Project skills (optional)
if [ -d ".claude/skills" ]; then
for skill_dir in .claude/skills/*/; do
[ -d "$skill_dir" ] || continue
skill_name=$(basename "$skill_dir")
if [ -f "$skill_dir/SKILL.md" ]; then
echo "✅ Skill: $skill_name"
else
echo "❌ Skill: $skill_name (missing SKILL.md)"
ERRORS=$((ERRORS+1))
fi
done
fi
# CLAUDE.md must exist
[ -f "CLAUDE.md" ] && echo "✅ Found: CLAUDE.md" || echo "⚠️ Missing: CLAUDE.md"
# .mcp.json at root (optional)
[ -f ".mcp.json" ] && echo "✅ Found: .mcp.json" || echo "ℹ️ Optional: .mcp.json not found"
# Memory index consistency (if memory exists)
if [ -f ".planning/memory/MEMORY.md" ]; then
grep -o '(memory/[^)]*)' .planning/memory/MEMORY.md | tr -d '()' | while read -r m; do
[ -f ".planning/$m" ] || echo "⚠️ Memory index points to missing file: $m"
done
for f in .planning/memory/*.md; do
[ "$(basename "$f")" = "MEMORY.md" ] && continue
if grep -q "status: active" "$f" 2>/dev/null; then
grep -q "$(basename "$f")" .planning/memory/MEMORY.md || echo "⚠️ Active memory not indexed: $(basename "$f")"
fi
done
fi
# Audit DB integrity (when enabled)
if grep -q '"audit"[[:space:]]*:[[:space:]]*true' .planning/config.json 2>/dev/null; then
if [ -f ".planning/pwdev-audit.db" ] && command -v sqlite3 >/dev/null 2>&1; then
sqlite3 .planning/pwdev-audit.db "PRAGMA integrity_check;" 2>/dev/null | head -1
else
echo "⚠️ Audit enabled but DB or sqlite3 missing"
fi
fi
echo "=== STRUCTURE ERRORS: $ERRORS ==="
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 · 244 lines · 27 tokens per session scan A a749b84a4900
health is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 2,420 once invoked, about $0.0001 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.