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 skills/vinilana/dotcontext/share-semantic-analysisnpx skills add vinilana/dotcontext --skill share-semantic-analysisgit clone --depth 1 https://github.com/vinilana/dotcontextWrote 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/vinilana/dotcontext/share-semantic-analysis)<a href="https://agentmods.dev/skills/vinilana/dotcontext/share-semantic-analysis"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/share-semantic-analysis.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.00061 | $0.00419 |
| Opus 5 | $0.00030 | $0.00210 |
| Sonnet 5 | $0.00012 | $0.00084 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
share-semantic-analysis 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.
What it actually says
Share Semantic Analysis
Compute one bounded analysis bundle per operation and reuse it.
Workflow
- Map every repository scan, glob, file read, parse, fingerprint, and derived output in the operation.
- Define one AnalysisBundle owner at the harness application boundary.
- Discover relevant files once with shared ignores.
- Parse each selected file once and derive symbols, architecture, and functional patterns from the same analyses.
- Pass the same bundle to documentation, agent, plan, and snapshot consumers.
- Apply file-count, per-file byte, total-byte, and concurrency limits.
- Mark partial analysis and skipped reasons explicitly.
- Release operation-scoped caches in finally.
Fingerprinting
Enumerate only relevant files. Reuse content hashes when path, size, and mtime are unchanged. Include dirty files when using git identity. Limit stabilization retries and keep the previous snapshot readable until publication succeeds.
Required invariants
- Never perform a second semantic read only to derive functional patterns.
- Never let generators silently create independent analyzers in the main context-init path.
- Never glob the entire repository and filter relevance only afterward.
- Never call an analysis complete after a configured limit was hit.
- Honor cacheEnabled.
- Keep snapshot publication atomic.
Dotcontext routing
- Own AnalysisBundle in src/harness/application/context.
- Keep parsing in semantic adapters.
- Inject data into generators instead of importing transport state.
- Follow F-05.
Review gate
Instrument tests to count discovery calls, file reads, parse calls, maximum concurrency, bytes read, and fingerprint attempts. Require one parse per selected file in default type=both context init.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 61 tokens per session scan A 54e4b4e7c13d
share-semantic-analysis is a skill published in the GitHub repository vinilana/dotcontext (565 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 419 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…