Borrowing it
Nothing to install: this file belongs to airiclenz/llama-launcher. 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/airiclenz/llama-launcher/main/AGENTS.mdgit clone --depth 1 https://github.com/airiclenz/llama-launcherWrote 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/airiclenz/llama-launcher/agents-md)<a href="https://agentmods.dev/instructions/airiclenz/llama-launcher/agents-md"><img src="https://agentmods.dev/badge/instructions/airiclenz/llama-launcher/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/airiclenz/llama-launcher/agents-md"><img src="https://agentmods.dev/badge/instructions/airiclenz/llama-launcher/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01056 | $0.01056 |
| Opus 5.5 | $0.00422 | $0.00422 |
| Sonnet 5.5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
llama-launcher 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 today.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Consult llama-launcher.TDD.md for all project details: architecture, build commands, coding standards, and contribution workflow.
Supported LLM Servers: llamacpp, ollama, lmstudio and splash — see the glossary Note (capcom know show glossary) for the domain terms and llama-launcher.TDD.md for how each one is driven.
Project knowledge lives in capcom's Knowledge tree (listed at the end of this file). Before
starting work, run capcom know tree --depth 2, then capcom know tree <id> to open a branch,
and capcom know show <id> on every Note whose title matches the task. --depth 2 prints the
top level and its direct children only.
Issues and knowledge: capcom
capcom is the issue register of record for this repository. Issues and Knowledge Notes are
markdown files under .capcom/, versioned with the code; track work there and nowhere else.
Without a capcom binary, install it from https://github.com/airiclenz/capcom#install.
capcom next: the most urgent ready issue, in fullcapcom ready: the issues ready to work on, most urgent firstcapcom show <id>: one issue in full, with what blocks itcapcom context <id>: the issue with its deps, plan and the Notes that apply; run it before you startcapcom start <id>: claim it and take the Tree lock before you startcapcom log <id> <text>: note progress as work landscapcom close <id> --reason <text>: close an issue; it names the issues this made readycapcom finish <id> --reason <text>: close it and free the Tree lock; it names the issue to work on nextcapcom reopen <id> --reason <text>: undo a closecapcom create --id <slug> --title <title> [--dep <id>]: file a new issuecapcom dep add <id> <dep-id>: make an issue wait for another;capcom dep list <id>shows both sidescapcom list --tree --depth 2: the outline of the issuescapcom know tree: the outline of the Knowledge tree;capcom know show <id>reads a Note
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.
- today Changed · +22 lines · +395 tokens per session f7f793769add
- 16d ago Changed · +9 lines · +173 tokens per session e9d1e5c0e582
- 17d ago Changed · -9 lines · -570 tokens per session 498a1f94a4a5
- 1mo ago First seen · 43 lines · 1,058 tokens per session scan A 896196070fb2
llama-launcher AGENTS.md is an instructions file published in the GitHub repository airiclenz/llama-launcher (2 stars, last pushed yesterday), licensed MIT. It adds 1,056 tokens to every session, about $0.0042 per session on Opus 5.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-25.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.