Borrowing it
Nothing to install: this file belongs to rajbos/ai-engineering-fluency. 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/rajbos/ai-engineering-fluency/main/.claude/skills/validate-editor-names/SKILL.mdgit clone --depth 1 https://github.com/rajbos/ai-engineering-fluencyWrote 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/rajbos/ai-engineering-fluency/validate-editor-names)<a href="https://agentmods.dev/skills/rajbos/ai-engineering-fluency/validate-editor-names"><img src="https://agentmods.dev/badge/skills/rajbos/ai-engineering-fluency/validate-editor-names/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/rajbos/ai-engineering-fluency/validate-editor-names"><img src="https://agentmods.dev/badge/skills/rajbos/ai-engineering-fluency/validate-editor-names.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.00110 | $0.01165 |
| Opus 5.5 | $0.00044 | $0.00466 |
| Sonnet 5.5 | $0.00022 | $0.00233 |
| Haiku 4.5 | $0.00011 | $0.00117 |
Grade A, and why
validate-editor-names 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Editor Names Skill
Checks that the CLI and the VS Code extension always agree on editor display names, and that every name has an icon in the webview icon map.
There are three sources of truth that must stay in sync:
| Source | File | Function / symbol |
|---|---|---|
| CLI path detector | cli/src/analysis.ts |
getEditorSourceFromPath |
| VS Code path detector | src/workspaceHelpers.ts |
getEditorTypeFromPath (delegates to detectToolEditorFromPath + detectVSCodeVariantFromPath) |
| Webview icon map | src/editorIcons.ts |
EDITOR_ICON_MAP (the EditorName union type is derived from it in vscode-extension/src/webview/shared/formatUtils.ts) |
The JetBrains plugin (and any future CLI-based consumer) gets its editor names
exclusively from the CLI via CliBridge.kt. If the CLI returns a raw
lowercase key instead of a friendly display name the UI falls back to the raw
key everywhere: chart labels, the session list, the stats command.
What the script checks
- CLI-only coverage — every unique name returned by
getEditorSourceFromPathexists inEDITOR_ICON_MAP. - VS Code-only coverage — every unique name returned by
getEditorTypeFromPathexists inEDITOR_ICON_MAP. - Cross-function consistency — for a canonical set of test paths the CLI and VS Code detectors return identical names. Any mismatch is a bug.
- Ordering invariants — warns if a broad path pattern (e.g.
/.copilot/) appears before a more specific one (e.g./.copilot/jb/) in the CLI function, which would cause the broad check to shadow the specific one.
Usage
# Run all checks and print a human-readable report
node .github/skills/validate-editor-names/validate-editor-names.js
# Machine-readable JSON (for CI / further processing)
node .github/skills/validate-editor-names/validate-editor-names.js --json
# Show help
node .github/skills/validate-editor-names/validate-editor-names.js --help
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.
- yesterday First seen · 93 lines · 110 tokens per session scan A 99bfeb8c8841
validate-editor-names is a skill published in the GitHub repository rajbos/ai-engineering-fluency (119 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,165 once invoked, about $0.0004 per session on Opus 5.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-10-26.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…