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 commands/smithdak/claude-marketplace/setupgit clone --depth 1 https://github.com/smithdak/claude-marketplaceWrote 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/setup)<a href="https://agentmods.dev/commands/smithdak/claude-marketplace/setup"><img src="https://agentmods.dev/badge/commands/smithdak/claude-marketplace/setup.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 | $0.00010 | $0.00764 |
| Opus 5 | $0.00005 | $0.00382 |
| Sonnet 5 | $0.00002 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
setup 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 4d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimizely Setup Command
Configure the Optimizely CMS analyzer for your project.
Usage
/optimizely:setup # Interactive setup
/optimizely:setup --generate-ignore # Generate .claudeignore file
What It Does
The setup command:
- Detects Project - Identifies Optimizely version and structure
- Validates Environment - Checks for required tools
- Generates Configuration - Creates .claudeignore if needed
- Provides Guidance - Shows recommended next steps
Setup Flow
Step 1: Project Detection
Detecting Optimizely project...
✓ Platform: Optimizely CMS 13.5
✓ .NET Version: 8.0
✓ Deployment: Self-Hosted
✓ Features: Content Delivery API, Forms
Step 2: Environment Check
Checking environment...
✓ .NET SDK: 8.0.100
✓ NuGet: Available
⚠️ No .claudeignore file (recommended)
Step 3: Generate .claudeignore
When using --generate-ignore:
Creating .claudeignore...
Generated: .claudeignore
Contents:
# Optimizely CMS Analyzer - Exclusion Patterns
# Generated: 2026-01-25
# Secrets and credentials
appsettings.Development.json
appsettings.Production.json
appsettings.*.json
!appsettings.json
connectionStrings.config
*.pfx
*.p12
*.key
*.pem
.env*
secrets/
# Build output
bin/
obj/
publish/
# IDE and tools
.vs/
.idea/
*.user
*.suo
# Package caches
packages/
node_modules/
# Test results
TestResults/
coverage/
# Logs
logs/
*.log
# Temporary files
*.tmp
*.temp
Step 4: Next Steps
Setup Complete!
Next steps:
1. Review .claudeignore exclusions
2. Run security scan:
/optimizely:security-scan
3. Run analysis:
/optimizely:analyze
4. Generate AI skills:
/optimizely:enhance
For help:
/optimizely:analyze --help
.claudeignore Template
The generated .claudeignore file excludes:
Secrets & Credentials
- Environment-specific appsettings
- Connection string files
- Certificates and keys
- Environment files
Build Output
- bin/ and obj/ directories
- Publish output
- Package caches
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.
- 4d ago First seen · 179 lines · 10 tokens per session scan A 22a49e7e0001
setup is a command published in the GitHub repository smithdak/claude-marketplace (3 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 764 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.