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/teaql/teaql-agent-kit/agents-mdgit clone --depth 1 https://github.com/teaql/teaql-agent-kitWhat 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.00573 | $0.00573 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
teaql-agent-kit 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — TeaQL Agent Kit
This repository publishes the build-teaql-app Agent Skill. For TeaQL
modeling, generation, or application work, read and follow
skills/build-teaql-app/SKILL.md.
Hard Requirements
- Work model-first: save complete KSML, evaluate it with the Generation Service, and fix all Errors before generation. Never run evaluation before the first complete model target exists.
- TeaQL application generation supports exactly these seven language families: Java, Rust, Go, Swift, Python, C#/.NET, and TypeScript. Kotlin/JVM applications are also supported through Java-generated libraries and the Java runtime; this is JVM interoperability, not an eighth generator/runtime. Do not infer support for an unlisted language. C++, Dart, Ruby, and other unlisted smaller language ecosystems are not supported. Do not substitute one language's generated API for another.
- Rust requires
cargo-teaqlexactly2.0.13. Verify it before every TeaQL operation; stop on any mismatch. - Java requires
io.teaql:teaql-maven-plugin:1.1.1or newer from the TeaQL Nexus releases repository. Use fully qualified Maven coordinates, nevermvn teaql:*. - Every Rust model-derived command, including assist, uses
cargo teaql --input <model> <command> .... - Rust generation uses only
rust-lib-coreandrust-app-console. - Never edit generated domain-library files.
- Read the generated application/workspace
AGENTS.mdand current object-specific assist before business code. Never guess generated methods. - Every query execution declares purpose and comment through the exact generated API for its language.
- Every write declares an audit reason through the exact generated API for its language. Never guess the spelling from Java or Rust examples.
- When evaluation reaches zero errors, send the model path and evaluation counts, then continue without waiting. Human Review runs in parallel.
- Report actual model, assist, policy, compile, test, runtime, and token/context evidence. Never invent savings or verification results.
- Every
<_value>in a constant object must explicitly provide every data field declared by that constant object, even when a field is nullable. Do not repeat_...metadata, version,createTime()/updateTime()fields, or the domain-root relationship injected by runtime Fix/Context.
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 · +4 lines · +67 tokens per session 63d003169147
- 2d ago First seen · 42 lines · 506 tokens per session scan A 4f745bfe314a
teaql-agent-kit AGENTS.md is an instructions file published in the GitHub repository teaql/teaql-agent-kit (2,803 stars, last pushed 2d ago), licensed MIT. It adds 573 tokens to every session, about $0.0029 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
opencode-primer AGENTS.md
AGENTS.md instructions for wesammustafa/opencode-primer, covering agents.md, what this repo is, repo layout, editing rules and always.
specialist-agent CLAUDE.md
Instructions for herbert-julio-azion/specialist-agent, covering claude.md - specialist agent, about, auto-dispatch rules, available agents and core agents.
wove copilot-instructions.md
Instructions for mits-pl/wove, covering wave terminal — copilot instructions, project rules, skill guides and preview server.
armada AGENTS.md
Instructions for rafmacalaba/armada, covering armada — build rules, the job, the team, repository conventions and adaptive delivery.
agent-ready-repo AGENTS.md
Instructions for eugenelim/agent-ready-repo, covering agents.md, project overview, rule lookups, documentation and development workflow.
skills AGENTS.md
Instructions for CometWorks/skills: You are an experienced developer of Space Engineers in-game scripts, mods, and plugins.