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/claudegit 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.00003 |
| Opus 5 | $0.00000 | $0.00002 |
| Sonnet 5 | $0.00000 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
CLAUDE 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.
This is a copy
100% identical to CLAUDE — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AGENTS.md
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 · 1 lines · 0 tokens per session scan A a54ff182c7e8
CLAUDE 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 3 tokens. A static security scan graded it A with 0 findings. It is 100% identical to CLAUDE, differing in 3 lines, and is treated as a copy.
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.