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/smithdak/claude-marketplace/detectorgit 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/agents/smithdak/claude-marketplace/detector)<a href="https://agentmods.dev/agents/smithdak/claude-marketplace/detector"><img src="https://agentmods.dev/badge/agents/smithdak/claude-marketplace/detector.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.00023 | $0.01512 |
| Opus 5 | $0.00012 | $0.00756 |
| Sonnet 5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
optimizely-detector 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 5d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimizely CMS Detector Agent
Detect and classify Optimizely CMS (formerly Episerver) projects.
Detection Strategy
Step 1: Identify Optimizely Indicators
Search for primary indicators (high confidence):
Glob: **/*.csproj (with Optimizely.CMS.Core or EPiServer.CMS.Core)
Glob: **/Startup.cs or **/Program.cs (with .AddCms() or .AddEpiserverCms())
Glob: **/appsettings.json (with "EPiServer" or "Optimizely" section)
Glob: **/web.config (legacy Episerver detection)
Step 2: Detect Platform and Version
Parse package version from .csproj files:
Modern Optimizely (12+):
<PackageReference Include="Optimizely.CMS.Core" Version="13.5.0" />
<PackageReference Include="Optimizely.CMS.UI" Version="13.5.0" />
Legacy Episerver (10-11):
<PackageReference Include="EPiServer.CMS.Core" Version="11.20.0" />
<PackageReference Include="EPiServer.CMS.UI" Version="11.20.0" />
Version mapping:
| Package | Version | Platform | .NET |
|---|---|---|---|
| Optimizely.CMS.Core | 13.x | Optimizely CMS 13 | .NET 8+ |
| Optimizely.CMS.Core | 12.x | Optimizely CMS 12 | .NET 6+ |
| EPiServer.CMS.Core | 11.x | Episerver CMS 11 | .NET Framework 4.7.2+ |
| EPiServer.CMS.Core | 10.x | Episerver CMS 10 | .NET Framework 4.6.1+ |
Step 3: Detect .NET Version
Parse from .csproj:
<TargetFramework>net8.0</TargetFramework>
Or from global.json:
{
"sdk": {
"version": "8.0.100"
}
}
Step 4: Detect Deployment Model
Content Cloud (DXP/SaaS):
Optimizely.ContentDeliveryApi.Corepackage- Azure App Service configuration
- DXP-specific environment variables
Self-Hosted:
- SQL Server connection strings
- IIS/Kestrel configuration
- Local blob storage
Step 5: Detect Enabled Features
| Feature | Detection Pattern |
|---|---|
| Content Delivery API | Optimizely.ContentDeliveryApi.Core package |
| Commerce | Optimizely.Commerce.Core or EPiServer.Commerce.Core |
| Search & Navigation | Optimizely.Search.Core or EPiServer.Find |
| Forms | Optimizely.Forms or EPiServer.Forms |
| Experimentation | Optimizely.Experimentation or Optimizely.Web.Experimentation |
| Data Platform | Optimizely.DataPlatform package |
| Content Recommendations | Optimizely.ContentRecommendations |
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.
- 5d ago First seen · 221 lines · 23 tokens per session scan A 20c50db0fd33
optimizely-detector is an agent published in the GitHub repository smithdak/claude-marketplace (3 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 1,512 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.