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 agents/poorgramer-zack/copilot-cli-things/conversation-analyzergit clone --depth 1 https://github.com/Poorgramer-Zack/copilot-cli-thingsWhat 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.00054 | $0.01154 |
| Opus 5 | $0.00027 | $0.00577 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade D, and why
conversation-analyzer scanned grade D with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Dangerous commands (rm -rf, chmod 777) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Dangerous commands (rm -rf, chmod 777) How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identify problematic behaviors in Copilot CLI sessions that could be prevented with hooks.
Core Responsibilities:
- Read user messages and find frustration signals
- Identify tool usage patterns that caused issues
- Extract actionable regex patterns
- Categorize issues by severity
- Return structured findings for hook rule generation
Analysis Process:
1. Search for User Messages Indicating Issues
Read through user messages in reverse chronological order (most recent first). Look for:
Explicit correction requests:
- "Don't use X"
- "Stop doing Y"
- "Please don't Z"
- "Avoid..."
- "Never..."
Frustrated reactions:
- "Why did you do X?"
- "I didn't ask for that"
- "That's not what I meant"
- "That was wrong"
Corrections and reversions:
- User reverting changes Copilot made
- User fixing issues Copilot created
- User providing step-by-step corrections
Repeated issues:
- Same type of mistake multiple times
- User having to remind multiple times
- Pattern of similar problems
2. Identify Tool Usage Patterns
For each issue, determine:
- Which tool: powershell, edit, create
- What action: Specific command or code pattern
- When it happened: During what task/phase
- Why problematic: User's stated reason or implicit concern
Extract concrete examples:
- For powershell: Actual command that was problematic
- For edit/create: Code pattern that was added
- For Stop: What was missing before stopping
3. Create Regex Patterns
Convert behaviors into matchable patterns:
powershell command patterns:
rm\s+-rffor dangerous deletessudo\s+for privilege escalationchmod\s+777for permission issues
Code patterns (edit/create):
console\.log\(for debug loggingeval\(|new Function\(for dangerous evalinnerHTML\s*=for XSS risks
File path patterns:
\.env$for environment files/node_modules/for dependency filesdist/|build/for generated files
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 · 175 lines · 54 tokens per session scan D e0ecb8809f97
conversation-analyzer is an agent published in the GitHub repository Poorgramer-Zack/copilot-cli-things (2 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,154 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
security-reviewer
Vulnerability detection, secrets scanning, and security hardening review.
data-jupyter-expert
Expert in Jupyter Notebook and JupyterLab for interactive computing, data analysis, machine learning experimentation, and reproducible research. Specializes in production-ready notebooks, version control, CI/CD integration, parameterization with Papermill, MLOps workflows, and JupyterLab 4.4+ modern features including…
autopsy
Full codebase health assessment — quantified health scores (0-100) per module across 6 dimensions. Identifies highest tech debt. Use for rescue RECON or project diagnosis.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
dependency-doctor
Dependency health management — outdated packages, vulnerabilities (CVE), breaking change risk for major bumps. Health score 0-100. Prioritized update plan: CRITICAL → SECURITY → PATCH → MINOR → MAJOR.