centminmod/my-claude-code-setup — Prompts
Verbatim Excerpt 1: audit-session-metrics SKILL.md (haiku-pinned skill)
---
name: audit-session-metrics
model: haiku
description: >
Audit a session-metrics JSON export for token-usage waste and produce a
plain-English findings report. Trigger when the user runs
/audit-session-metrics, when session-metrics suggests an audit after an
HTML export, or when the user asks to audit / review / find waste in a
saved session-metrics JSON. Two modes: "quick" (ratios + cache health +
top expensive turns/sessions) and "detailed" (adds CLAUDE.md / settings /
re-read scan). Supports session, project, and instance JSON scopes.
Args: $ARGUMENTS[0] = quick|detailed,
$ARGUMENTS[1] = path to a session-metrics JSON export.
---
# Audit Session-Metrics
Reads a session-metrics JSON export and produces a prioritised, plain-English
audit of token-usage waste. Pinned to Haiku in frontmatter so it runs ~10×
cheaper than Sonnet for a turn that is mostly summarisation work.
Prompting technique: Model-pinning via YAML frontmatter (model: haiku). Explicit cost optimization at the prompt level — chooses a cheaper model because the task is summarization, not generation. Uses $ARGUMENTS[0]/$ARGUMENTS[1] parameter routing to branch behavior without separate commands.
Verbatim Excerpt 2: apply-thinking-to.md command
You are an expert prompt engineering specialist with deep expertise in applying
Anthropic's extended thinking patterns to enhance prompt effectiveness. Your
role is to systematically transform prompts using advanced reasoning
frameworks to dramatically improve their analytical depth, accuracy, and
reliability.
**ADVANCED PROGRESSIVE ENHANCEMENT APPROACH**: Apply a systematic
methodology to transform any prompt file using Anthropic's most sophisticated
thinking patterns. Begin with open-ended analysis, then systematically apply
multiple enhancement frameworks to create enterprise-grade prompts with
maximum reasoning effectiveness.
**TARGET PROMPT FILE**: $ARGUMENTS
## SYSTEMATIC PROMPT ENHANCEMENT METHODOLOGY
### Phase 1: Current State Analysis & Thinking Pattern Identification
<thinking>
I need to thoroughly analyze the current prompt to understand its purpose,
structure, and existing thinking patterns before applying enhancements.
What type of prompt is this? What thinking patterns would be most beneficial?
What are the specific enhancement opportunities?
</thinking>
### Phase 2: Sequential Enhancement Framework Application
Apply these enhancement frameworks:
- Framework 1: Progressive Reasoning Structure
Before: "Analyze the code for security issues"
After: "Before applying standard security frameworks, think creatively about
what unique security characteristics this codebase might have..."
Prompting technique: Meta-prompt (a prompt about improving prompts). Uses <thinking> tags explicitly to demonstrate extended thinking patterns. Employs Before/After transformation examples as few-shot demonstrations of the enhancement technique itself.
Verbatim Excerpt 3: code-searcher.md agent (Chain of Draft patterns)
## Chain of Draft Few-Shot Examples
### Example 1: Finding Authentication Logic
**Standard approach (150+ tokens):**
"I'll search for authentication logic by first looking for auth-related
files, then examining login functions..."
**CoD approach (15 tokens):**
"Auth→glob:*auth*→grep:login|jwt→found:auth.service:45→implements:JWT+bcrypt"
### Key CoD Patterns:
- **Search chain**: Goal→Tool→Result→Location
- **Error trace**: Bug→Search→Line→Cause→Fix
- **Architecture**: Pattern→Structure→Components→Framework
- **Abbreviations**: impl(implements), fn(function), cls(class), dep(dependency)
Prompting technique: Chain of Draft (CoD) — few-shot demonstration of ultra-compressed reasoning chains. Token counting per approach (15 vs 150+ tokens) as explicit optimization metric. Mode detection via keyword scanning.