Borrowing it
Nothing to install: this file belongs to raghavwahi/semdex-mcp-server. 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/raghavwahi/semdex-mcp-server/main/.claude/skills/sdx-inspect/SKILL.mdgit clone --depth 1 https://github.com/raghavwahi/semdex-mcp-serverWrote 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/skills/raghavwahi/semdex-mcp-server/sdx-inspect)<a href="https://agentmods.dev/skills/raghavwahi/semdex-mcp-server/sdx-inspect"><img src="https://agentmods.dev/badge/skills/raghavwahi/semdex-mcp-server/sdx-inspect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/raghavwahi/semdex-mcp-server/sdx-inspect"><img src="https://agentmods.dev/badge/skills/raghavwahi/semdex-mcp-server/sdx-inspect.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00303 |
| Opus 5 | $0.00015 | $0.00151 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
sdx-inspect 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 11d 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.
What it actually says
Inspect Semdex Index
Quick Health Check
sdx inspect --stats
Shows: total chunks, chunk types breakdown, indexed file count, parse failures, embedding model status, last index timestamp, git commit at index time.
Inspect Specific File
sdx inspect --file src/foo.ts
Lists every chunk extracted from that file with: canonical type, name, line range, content hash, git commit.
Inspect Specific Symbol
sdx inspect --symbol UserService
Shows: definition location, callers, imports, and associated edges.
List Parse Failures
sdx inspect --failed
Shows files that failed to parse with Tree-sitter error details.
What to Check
- If chunk count is zero, verify the repo was indexed (
sdx indexfirst) - If many parse failures, check Tree-sitter grammar compatibility
- If model status shows "unavailable," run
sdx initto re-download - If git commit doesn't match HEAD, the index is stale — re-index
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.
- 11d ago First seen · 49 lines · 30 tokens per session scan A 13cdbf49bbbc
sdx-inspect is a skill published in the GitHub repository raghavwahi/semdex-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 303 once invoked, about $0.0002 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 skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.