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 instructions/jankowskim/lory/agents-mdgit clone --depth 1 https://github.com/jankowskim/loryWhat 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.01710 | $0.01710 |
| Opus 5 | $0.00855 | $0.00855 |
| Sonnet 5 | $0.00342 | $0.00342 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
lory AGENTS.md 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 2d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Build & Test
cargo build --workspace # Build all crates
cargo test --workspace # Run all tests
cargo clippy --workspace -- -D warnings # Lint (must pass before commit)
cargo fmt --check # Format check
cargo deny check # License/advisory audit (if deny.toml exists)
Run tests AND clippy before every commit. Both must pass.
Project Structure
Three-crate Cargo workspace:
- lory-core — Library. ALL business logic lives here.
- lory-cli — Binary (
lory). Thin adapter over lory-core. - lory-mcp — Binary (
lory-mcp). MCP server, thin adapter over lory-core.
Put logic in lory-core, not in the binary crates.
Rust Conventions
- Edition: 2024. MSRV: 1.88+.
- Errors:
thiserrorin lory-core. Binary crates propagateLoryErrorfrom core. No.unwrap()in library code. - Visibility: Default
pub(crate). Onlypubfor lory-core's public API. - SQL: Parameterized queries only. Never interpolate user input.
Issue Tracking with bd (beads)
IMPORTANT: This project uses bd (beads) for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
Why bd?
- Dependency-aware: Track blockers and relationships between issues
- Git-friendly: Dolt-powered version control with native sync
- Agent-optimized: JSON output, ready work detection, discovered-from links
- Prevents duplicate tracking systems and confusion
Quick Start
Check for ready work:
bd ready --json
Create new issues:
bd create "Issue title" --description="Detailed context" -t bug|feature|task -p 0-4 --json
bd create "Issue title" --description="What this issue is about" -p 1 --deps discovered-from:bd-123 --json
Claim and update:
bd update <id> --claim --json
bd update bd-42 --priority 1 --json
Complete work:
bd close bd-42 --reason "Completed" --json
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.
- 2d ago First seen · 204 lines · 1,710 tokens per session scan A c170c000f514
lory AGENTS.md is an instructions file published in the GitHub repository jankowskim/lory (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,710 tokens to every session, about $0.0086 per session on Opus 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-08-31.
Other instructions, from other repositories
warrant AGENTS.md
Instructions for s0fractal/warrant, covering agent & contributor conduct (governance-critical), hard rules, the human's role and precedent (why this file exists).
adc AGENTS.md
Instructions for dbrattli/adc, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
redraft CLAUDE.md
Instructions for KaelinGraf/redraft, covering redraft (engine), running tests, rebuilding the ui and the organizing protocol.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.