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/outlmd/outl/checkgit clone --depth 1 https://github.com/outlmd/outlWhat 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.00019 | $0.00270 |
| Opus 5 | $0.00010 | $0.00135 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
check 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.
What it actually says
Run in sequence and report the result of each step:
cargo fmt --all -- --check— formattingcargo clippy --workspace --all-targets -- -D warnings— lintscargo test --workspace --all-targets— testsRUSTDOCFLAGS="-D warnings" cargo doc --workspace --no-deps— docs (CI runs this; breaks on intra-doc links to private items, e.g.[`Foo`]whereFooispub(crate). Drop the brackets:`Foo`.)
If any step fails, stop and show the exact output. Do not attempt to fix automatically — only report.
Output format:
fmt: PASS | FAIL (N files)
clippy: PASS | FAIL (N warnings)
test: PASS | FAIL (N failures)
doc: PASS | FAIL (N warnings)
[failure details, if any]
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 · 27 lines · 19 tokens per session scan A 811040f2c227
check is a command published in the GitHub repository outlmd/outl (161 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 270 once invoked, about $0.0001 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-09-01.
Other commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.