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 commands/lodyai/lody/global-shortcutsgit clone --depth 1 https://github.com/LodyAI/LodyWhat 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.00000 | $0.00489 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
global-shortcuts 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configurable OS-level global shortcuts
Global shortcuts do not use the renderer command registry. Electron main registers
them with globalShortcut.register, so they can run while the app is unfocused.
Cross-process path
-
Shared source of truth:
@lody/shared/electron-ipcGlobalShortcutIdandGLOBAL_SHORTCUT_DEFAULTSdefine ids and default binding strings such asCtrl+Alt+Lfor both processes.- IPC contracts are
GlobalShortcutBinding,SetGlobalShortcutInput,SetGlobalShortcutResult, andGlobalShortcutSetError. bindingToElectronAcceleratorconverts a binding to an Electron accelerator and rejects invalid or modifier-free bindings. A global bare key would consume that key across the OS. Pure conversion tests live inpackages/shared/tests/global-shortcut-accelerator.test.ts.
-
Main process:
apps/electron/src/main/services/global-shortcuts-service.tsGlobalShortcutsServicepersists per-user overrides throughConf, registers the effective bindings, atomically replaces a binding with rollback on conflict, and unregisters everything during disposal.binding: nullis an explicit unbind.createGlobalShortcutsServicein main injects the behavior handlers; the service owns registration/persistence rather than window behavior.app.getGlobalShortcutsandapp.setGlobalShortcutvalidate IPC input. A trigger sendsapp.globalShortcut(GLOBAL_SHORTCUT_TRIGGERED_CHANNEL) to an available renderer, which owns any analytics event.
-
Renderer:
lib/native-global-shortcuts.tsprovides a null-safe API wrapper,hooks/use-global-shortcuts.tsloads and updates bindings, andGlobalShortcutRowin keyboard settings provides recording, validation, conflict feedback, and unbind.GLOBAL_SHORTCUTSinshortcuts.tsis presentation-only.
Adding a shortcut
- Add the id and default binding to
@lody/shared. - Add
{ id, handler }tocreateGlobalShortcutsService. - Add the presentation entry and i18n title to
GLOBAL_SHORTCUTS.
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 · 41 lines · 0 tokens per session scan A d4fdca8f5d01
global-shortcuts is a command published in the GitHub repository LodyAI/Lody (801 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 489 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-30.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
speckit.extract
Extract ADRs, knowledge, and guidelines from completed specifications into dev/ documentation.