Borrowing it
Nothing to install: this file belongs to yazinsai/tilawa. 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/yazinsai/tilawa/main/AGENTS.mdgit clone --depth 1 https://github.com/yazinsai/tilawaWrote 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/yazinsai/tilawa/agents-md)<a href="https://agentmods.dev/instructions/yazinsai/tilawa/agents-md"><img src="https://agentmods.dev/badge/instructions/yazinsai/tilawa/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.01281 | $0.01281 |
| Opus 5 | $0.00641 | $0.00641 |
| Sonnet 5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
tilawa 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 7d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tilawa
Offline Quran verse recognition — give it 16kHz audio, get surah:ayah. Fully on-device (web / node / React Native).
This repo ships two things:
@tilawa/core(packages/core/) — the SDK. Pure TypeScript: CTC decode +QuranDBverse matching + streaming tracker. Zero native deps; the app dev injects an ONNXSessionRunner.- Web demo (
web/) — live browser recitation demo that consumes@tilawa/coreas its regression guard.
The Python research/training/benchmark harness lives under lab/ and has its own lab/AGENTS.md. Model weights are proven out there, then their logic graduates into the SDK.
Layout
packages/core/ # @tilawa/core SDK (the shipped product)
src/
index.ts # createTilawaSession(runner, assets) + TilawaSession, TilawaAssets
session.ts # SessionRunner injection seam (type-only, no onnxruntime)
quran-db.ts # QuranDB — verse matching (bestJoint03Match)
tracker.ts # RecitationTracker — streaming verse detection
text-ctc-decode.ts # TextCTCDecoder — logprobs -> text
quran-text-adapter.ts# adaptQuranTextData / validateCtcTokenRoundTrip
ctc-rescore.ts, levenshtein.ts, normalizer.ts, types.ts # pure helpers
test/ # deterministic vitest (decode+match, no ONNX)
web/ # live browser demo (Vite + worker), consumes @tilawa/core
frontend/src/worker/session.ts # the web SessionRunner (onnxruntime-web)
lab/ # Python research/training/benchmark harness — see lab/AGENTS.md
README.md, Dockerfile, LICENSE
SDK architecture
The working pipeline cleanly splits into:
- Pure-TS core —
quran-db,tracker,text-ctc-decode,quran-text-adapter,ctc-rescore,levenshtein,normalizer,types. Zero ONNX imports. - ONNX boundary — a single
SessionRunnerinterface the app dev injects. Contract: inputaudio_signal [1,N]float32 +length, output[1,T,vocab]logprobs. Preprocessing is baked into the ONNX graph.
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.
- 7d ago First seen · 110 lines · 1,281 tokens per session scan A 71b27c869810
tilawa AGENTS.md is an instructions file published in the GitHub repository yazinsai/tilawa (263 stars, last pushed 2mo ago), licensed MIT. It adds 1,281 tokens to every session, about $0.0064 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
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).
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.
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 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).
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.