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.
git clone --depth 1 https://github.com/keska-labs/enterprise-skillsWrote 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/rules/keska-labs/enterprise-skills/extension-host)<a href="https://agentmods.dev/rules/keska-labs/enterprise-skills/extension-host"><img src="https://agentmods.dev/badge/rules/keska-labs/enterprise-skills/extension-host/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/rules/keska-labs/enterprise-skills/extension-host"><img src="https://agentmods.dev/badge/rules/keska-labs/enterprise-skills/extension-host.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.00000 | $0.00334 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
extension-host 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 10d 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
Extension host (src/)
Composition
- Wire dependencies in
src/extension.ts: construct services once, pass into panels andSyncEngine. - Register everything that implements
vscode.Disposableviacontext.subscriptions.push(...).
Errors and logging
- Use
Loggerfor diagnostics (log,warn,error). The output channel is the primary trace for support. - Throw or propagate
ServiceErrorwith a stablereason(no_session,network,source_invalid, …) when the failure maps to user-visible connection/sync health; panels map reasons to UI state where needed.
Async
- Use
async/await. At fire-and-forget boundaries (e.g. event handlers), usevoid this.someAsync()or.catch(...)so unhandled rejections do not crash the host.
VS Code API
- Externalize
vscodein webpack; never bundle it. Tests use Jest’svscodealias tosrc/test/vscodeMock.ts.
Sync and config
ConfigServicereads/writesskillSync.*keys only.SyncEngineowns periodic sync and emits results; do not duplicate sync loops elsewhere.
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.
- 10d ago First seen · 32 lines · 0 tokens per session scan A e98412dacf37
extension-host is a cursor rule published in the GitHub repository keska-labs/enterprise-skills (7 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 334 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.