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/.github/prompts/sync-toolnames.prompt.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/commands/rajbos/ai-engineering-fluency/sync-toolnames)<a href="https://agentmods.dev/commands/rajbos/ai-engineering-fluency/sync-toolnames"><img src="https://agentmods.dev/badge/commands/rajbos/ai-engineering-fluency/sync-toolnames/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/commands/rajbos/ai-engineering-fluency/sync-toolnames"><img src="https://agentmods.dev/badge/commands/rajbos/ai-engineering-fluency/sync-toolnames.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.00024 | $0.00948 |
| Opus 5.5 | $0.00010 | $0.00379 |
| Sonnet 5.5 | $0.00005 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
sync-toolnames 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Tool Names from vscode-copilot-chat
Scan microsoft/vscode-copilot-chat repo for model-facing tool identifiers, compare them to the existing src/toolnames.json in our repo in the current folder. Only make changes in our current folder.
Requirements
- The
microsoft/vscode-copilot-chatrepository has been checked out and is available in the workspace in the foldervscode-copilot-chat. Use the paths provided in the Context Paths section below. - In the vscode-copilot-chat repo, treat
src/extension/tools/common/toolNames.tsas the source of truth for tool IDs.- Extract tool IDs from:
export enum ToolName { ... }(string literal values)export enum ContributedToolName { ... }(string literal values)
- Ignore TypeScript keys (enum member names). Only collect the string values (the model-facing tool names).
- Extract tool IDs from:
- In this repo, load the existing mapping file
src/toolNames.json. Treat its top-level keys as the set of already-known tool IDs. - Normalize and deduplicate before computing missing:
- Use the helper at
.github/scripts/toolnames_utils.py(or replicate its canonicalization rules) to canonicalize both upstream tool IDs and existing mapping keys. - Equivalent forms (e.g.
mcp_github_github_*↔mcp_io_github_git_*↔github-mcp-server-*,context7-*↔mcp_context7_*, Playwright/Tavily/Claude Browser prefix variants) must collapse to the same canonical key. - Compute
missing = upstream IDs whose canonical form is not already present in the existing mapping. - Skip any upstream ID whose generated friendly name already exists as a value in
toolNames.json. - Deduplicate.
- Sort ascending (stable, locale-insensitive).
- Use the helper at
- For each missing tool ID, generate a default friendly name:
- Replace
_/-/.with spaces. - Split camelCase / PascalCase boundaries into words.
- Uppercase words (Title Case).
- Preserve known acronyms in ALL CAPS:
VSCODE,MCP,GITHUB,API,URL,JSON,HTTP,HTTPS,CLI,UI,IO,ID. - Examples:
github_api_tool→GitHub API Toolcopilot_readFile→Copilot Read Filemcp.io.github.git→MCP IO GitHub Gitsearch_subagent→Search Subagentrun_in_terminal→Run In Terminalvscode_command→VSCode Command
- Replace
- Inject only the missing entries into our existing mapping object in the current repository, using the same style as the mapping (leading comma with space on each line), e.g.:
, "some_tool": "Some Tool" - Inject the missing entries inside the json object, matching the organic grouping of locically related tools if possible (e.g. if there are existing entries with the same prefix, group the new entry with them). If no related entries exist, add the new entry at the end of the file, but before the closing
}. - Also print (as plain text, after the delta or NO_DELTA) the upstream commit SHA used for the scan and the exact file path scanned in upstream, for traceability.
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 · 51 lines · 24 tokens per session scan A 26d6e02669df
sync-toolnames is a command published in the GitHub repository rajbos/ai-engineering-fluency (119 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 948 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.