Borrowing it
Nothing to install: this file belongs to crimson-knight/llamero. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/crimson-knight/llamero/main/AGENTS.mdgit clone --depth 1 https://github.com/crimson-knight/llameroWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/crimson-knight/llamero/agents-md)<a href="https://agentmods.dev/instructions/crimson-knight/llamero/agents-md"><img src="https://agentmods.dev/badge/instructions/crimson-knight/llamero/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.01727 | $0.01727 |
| Opus 5 | $0.00864 | $0.00864 |
| Sonnet 5 | $0.00345 | $0.00345 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
llamero 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 8d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
llamero — agent quick reference
llamero is a Crystal library for AI applications: cloud provider clients
(OpenAI, Anthropic, Groq, OpenRouter) with failover, plus native local
inference and LoRA/QLoRA adapter training on Apple Silicon via MLX. One
require: require "llamero".
This file is the condensed API contract. Fuller task recipes live in the
shipped skills: cloud-providers, local-inference, adapter-training
(installed as .claude/skills/llamero--<name>/ in consuming projects).
Cloud chat with failover
require "llamero"
class MyAIClient < Llamero::Client # abstract base - MUST subclass
def initialize
super(primary: :openai, fallbacks: [:anthropic, :groq])
end
end
client = MyAIClient.new
response = client.chat([Llamero::Message.user("Hello!")])
puts response.content
Keys via env vars: OPENAI_API_KEY, ANTHROPIC_API_KEY, GROQ_API_KEY,
OPENROUTER_API_KEY. Streaming: client.chat_stream(messages) { |chunk| print chunk }.
Direct clients without failover: Llamero::OpenAIClient.new,
Llamero::AnthropicClient.new, Llamero::GroqClient.new,
Llamero::OpenRouterClient.new.
Structured JSON output (cloud and local, same pattern)
class PersonInfo < Llamero::BaseGrammar
property name : String = "" # every property needs a default
property age : Int32 = 0
end
response = client.chat_structured([Llamero::Message.user("Random person")], PersonInfo)
person = response.parsed.not_nil!
Storage root for consuming apps
Default storage is ~/.llamero. Apps that need app-owned AI data set this at
boot before creating runtimes:
Llamero.storage_root = Path.home.join(".scribe")
LLAMERO_HOME=/path/to/root is the env alternative; programmatic wins. The
root controls models/, adapters/, bridge lib/ lookup, and configured
audio model caches under audio_models/. FluidAudio 0.15.2 still pins English
Kokoro G2P assets to its own TTS cache; see
development_docs/storage_configuration.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.
- 8d ago First seen · 157 lines · 1,727 tokens per session scan A f83b331a907f
llamero AGENTS.md is an instructions file published in the GitHub repository crimson-knight/llamero (22 stars, last pushed 15d ago), licensed MIT. It adds 1,727 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
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.