Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-cli/main/.claude/commands/analyze.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/analyze)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/analyze"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/analyze.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.00000 | $0.01304 |
| Opus 5 | $0.00000 | $0.00652 |
| Sonnet 5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
analyze 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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analyze
allowed-tools: mcp__zen__analyze(), mcp__zen__codereview(), mcp__zen__secaudit(), Task(), Read(), Bash(), Glob(), Grep(), mcp__gemini__, mcp__search-repo-docs__, mcp__ask-repo-agent__, mcp__genie_memory__, mcp__send_whatsapp_message__, mcp__wait__ description: Unified analysis command supporting general analysis, multi-agent code review, and security/performance audits
Comprehensive analysis command that unifies general analysis, multi-agent code review, and specialized security/performance audits with intelligent mode selection.
Auto-Loaded Project Context:
@/CLAUDE.md @/docs/ai-context/project-structure.md @/docs/ai-context/docs-overview.md
Analysis Modes
General Analysis (default)
# Default comprehensive analysis
/analyze "Review the authentication system architecture"
/analyze "Analyze database performance" model="o3"
Multi-Agent Code Review
# Multi-expert code review (replaces /review)
/analyze "Latest commit for security issues" mode="review"
/analyze "agents/routing/handler.py for performance" mode="review"
/analyze "Authentication system implementation" mode="review"
Security Audit
# Security-focused analysis (replaces /check security focus)
/analyze "Security audit of API endpoints" mode="security"
/analyze "User input validation" mode="security"
/analyze "Review authentication flow" mode="security"
Performance Analysis
# Performance-focused analysis (replaces /check performance focus)
/analyze "Database queries" mode="performance"
/analyze "Payment processing bottlenecks" mode="performance"
/analyze "Memory usage in agent sessions" mode="performance"
Quality Assessment
# Code quality analysis (replaces /check quality focus)
/analyze "Code quality in agents/" mode="quality"
/analyze "Maintainability review" mode="quality"
Model Strengths
- Claude (default): Comprehensive analysis with project context
- O3: Logical analysis, systematic evaluation, code review
- Grok: Large context analysis (256K tokens), performance analysis
- Gemini: Architectural insights, security patterns, creative solutions
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.
- 3d ago First seen · 167 lines · 0 tokens per session scan A 31ee81376823
analyze is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,304 tokens. 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-09-04.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.