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/pilot617/awesome-claude-code-plugins/cw-debugnpx skills add pilot617/awesome-claude-code-plugins --skill cw-debuggit clone --depth 1 https://github.com/pilot617/awesome-claude-code-pluginsWhat 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.00002 | $0.01974 |
| Opus 5 | $0.00001 | $0.00987 |
| Sonnet 5 | $0.00000 | $0.00395 |
| Haiku 4.5 | $0.00000 | $0.00197 |
Grade A, and why
cw-debug 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 2d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cw-debug — CloudWatch Log Investigation Skill
You are investigating a production issue using CloudWatch Logs Insights. Follow the structured methodology below, adapting queries based on what you discover in each phase.
Arguments
The user will invoke this skill as:
/cw-debug <log_group> <filter_pattern> <hours_back> <region> "<issue_description>"
log_group: The CloudWatch log group path (e.g.,/aws/ecs/my-service)filter_pattern: Any string to filter logs — a user ID, request ID, service name, error code, or any identifier relevant to the investigationhours_back: How many hours of logs to search (e.g.,24,168for 7 days)region: AWS region (e.g.,us-east-1)issue_description: Free-text description of the problem being investigated (bug, performance issue, unexpected behavior, etc.)
Setup
- Always use
.venv/bin/pythonto run scripts - The skill has its own self-contained CloudWatch utility at
${CLAUDE_PLUGIN_ROOT}/skills/cw-debug/scripts/cw.py - Do NOT import from
cloudwatch_utils.py— use the skill's own module instead - To use in inline scripts, add the scripts dir to
sys.paththen import:import sys, os sys.path.insert(0, os.path.expanduser("${CLAUDE_PLUGIN_ROOT}/skills/cw-debug/scripts")) from cw import CWClient cw = CWClient(region="{region}") results = cw.query("{query}", hours_back={hours_back}, log_group="{log_group}") cw.print_table(results) - Or use the CLI directly:
.venv/bin/python ${CLAUDE_PLUGIN_ROOT}/skills/cw-debug/scripts/cw.py \ --region {region} --log-group "{log_group}" --hours {hours_back} \ --query "fields @timestamp, @message | limit 25" - Available
CWClientmethods:cw.query(query_string, hours_back, log_group)— single log group querycw.query_multi(query_string, hours_back, log_groups)— query multiple log groups, merge results with_log_grouptagCWClient.summarize_stats(results, value_field, group_field=None)— compute count/avg/min/p50/p90/p95/p99/max from fetched resultsCWClient.time_bucket_counts(results, timestamp_field, bucket_minutes)— group into time buckets for spike detectionCWClient.print_table(results)— ASCII table outputCWClient.print_json(results)— JSON outputcw.save(results, name)— save toinvestigations/<name>.csv
- Refer to
${CLAUDE_PLUGIN_ROOT}/skills/cw-debug/query_library.mdfor pre-built query templates
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 170 lines · 2 tokens per session scan A 818054308da8
cw-debug is a skill published in the GitHub repository pilot617/awesome-claude-code-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 2 tokens to every session and 1,974 once invoked, about $0.0000 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
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
crossing-the-chasm
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
conversion-optimization
Guided journey from a leaking conversion flow - landing page, signup, checkout, or in-app onboarding - to a measured, tested funnel. Orchestrates six skills phase by phase - lean-analytics, cro-methodology, storybrand-messaging, hundred-million-offers, influence-psychology, design-everyday-things - each phase carries…