Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/smithdak/claude-marketplacenpx agentmods add commands/smithdak/claude-marketplace/analyzeWrote 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/smithdak/claude-marketplace/analyze)<a href="https://agentmods.dev/commands/smithdak/claude-marketplace/analyze"><img src="https://agentmods.dev/badge/commands/smithdak/claude-marketplace/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.00020 | $0.02530 |
| Opus 5 | $0.00010 | $0.01265 |
| Sonnet 5 | $0.00004 | $0.00506 |
| Haiku 4.5 | $0.00002 | $0.00253 |
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 7d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimizely CMS Analyzer
Analyze Optimizely CMS (formerly Episerver) projects with comprehensive checks for architecture, security, content modeling, and performance.
Usage
/optimizely:analyze # Run all agents
/optimizely:analyze all # Run all agents (explicit)
/optimizely:analyze architecture # Project structure only
/optimizely:analyze content-modeling # Content types only
/optimizely:analyze security # Security checks only
/optimizely:analyze performance # Performance analysis only
/optimizely:analyze quality # Code quality only
/optimizely:analyze dependencies # NuGet analysis only
/optimizely:analyze conventions # Naming/structure only
/optimizely:analyze experimentation # A/B testing integration only
Report Output
By default, the analysis report is written to a markdown file in the docs/ directory.
Output Options
| Option | Description |
|---|---|
| (default) | Write to docs/optimizely-analysis-{date}.md |
--output <path> |
Custom output path |
--no-file |
Display report only, don't write to file |
--safe-mode |
Analyze structure only, don't read file contents |
--severity <level> |
Filter issues by minimum severity: critical, warning, or info |
--baseline <path> |
Suppress known issues listed in baseline file |
--changes-only |
Only analyze files changed since last commit (git diff) |
Examples
# Default: writes to docs/optimizely-analysis-2026-01-25.md
/optimizely:analyze
# Custom output path
/optimizely:analyze --output ./reports/latest.md
# Display only, no file output
/optimizely:analyze --no-file
# Safe mode: structure only
/optimizely:analyze --safe-mode
File Output Behavior
When generating the report:
-
Create the output directory if it doesn't exist:
mkdir -p docs -
Generate filename with timestamp:
- Format:
optimizely-analysis-YYYY-MM-DD.md - If file exists, append time:
optimizely-analysis-YYYY-MM-DD-HHmmss.md
- Format:
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.
- 7d ago First seen · 356 lines · 20 tokens per session scan A f87e1f1d97d8
analyze is a command published in the GitHub repository smithdak/claude-marketplace (3 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 2,530 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.