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/agentsgit 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.00947 |
| Opus 5 | $0.00000 | $0.00474 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
AGENTS 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lib/commands command and shortcut system
CLAUDE.md is a symlink to this file. Edit AGENTS.md only.
This directory is the source of truth for application-level shortcuts, the command registry, the command palette, and keyboard-shortcut settings. Local interactions such as dialog Escape, list j/k, or composer Submit stay in their component key handlers.
KeyScope lets local and application-level shortcuts negotiate ownership. For example,
when a rich-text editor owns focus, Cmd+B must format text rather than toggle the
sidebar. A scope is not a command: it is not listed, configurable, or executable. It
only tells global dispatch to yield for events originating in its subtree.
Invariants
when()is the sole command-availability predicate. Both palette visibility and dispatch honor it; do not add screen-specific filters elsewhere.built-ins.tsregisterswhen: () => falseplaceholders so configurable shortcuts remain visible when their real component is unmounted. A mounted implementation shadows the placeholder and removal restores it.- The registry is a per-id stack. Multiple
registercalls push implementations and the most recently mounted one wins. Hidden retained tabs/toolbars must passenabled=falsetouseCommandor they can shadow the active surface. - Binding-level
whenlimits only the default binding. User overrides do not inherit it. Command-levelwhenlimits the command through every execution path. useKeyScope(id, ref)registers a scope and automatically removes it. Dispatch finds scopes containingevent.target, preferring the innermost. A matched scope yields all app shortcuts unless the command hasallowInTextInput: true;claimsnarrows the yielded bindings.- A scope that yields an event must not call
preventDefault: the editor/local keymap still needs to receive it. This applies after a shortcut is rebound as well. $modmeans Command on macOS and Control elsewhere. Formatting is platform-aware.- Alt+letter matching and recording must use
event.code; macOSevent.keymay be a generated glyph such as∫. - Shortcut capture pauses dispatch. It finishes after the last modifier is released and keeps a one-second settle window because macOS may suppress letter keyup while Command remains held.
- User bindings are per-device localStorage state.
[]explicitly unbinds all defaults;nullrestores defaults.
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.
- 3d ago First seen · 73 lines · 0 tokens per session scan A 6c6bca4e3ea8
AGENTS is a command published in the GitHub repository LodyAI/Lody (801 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 947 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
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
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.
release
Cut a release — bump all workspace versions in sync, generate/update CHANGELOG.md from Conventional Commits, commit and tag (push gated on confirmation).
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.