Borrowing it
Nothing to install: this file belongs to Dhairya3391/kari. 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/Dhairya3391/kari/main/AGENTS.mdgit clone --depth 1 https://github.com/Dhairya3391/kariWrote 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/dhairya3391/kari/agents-md)<a href="https://agentmods.dev/instructions/dhairya3391/kari/agents-md"><img src="https://agentmods.dev/badge/instructions/dhairya3391/kari/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.00717 | $0.00717 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
kari 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines
Short, mandatory rules for any AI agent modifying this codebase.
The full standard — structure, naming, comments, patterns — is
docs/CODEBASE.md. It wins over any habit or external convention.
1. Core Mandates
- Follow
docs/CODEBASE.mdexactly: every exported identifier gets a doc comment; comments explain why, not what; no dead code; simple over clever. - No Global Mutables: no global variables, no
init()side effects. Construct everything ininternal/app/app.goand pass it down. The one sanctioned exception isinternal/tui/styles.go's theme/style vars (colorPrimaryand friends) — lipgloss's idiomatic pattern; see the comment there. - Provider isolation: provider knowledge lives only under
internal/provider/**. Providers declare optional capabilities (AudioLanguagesSource,MovieEpisodeFlow,FeatureSource,StreamingProvider) instead of TUI/service branching on names or modes. New providers are registered only ininternal/provider/defaults. - Type ownership: providers keep their API types private in their own
package; shared wire DTOs live in
internal/provider; playback aggregates ininternal/model. No field-for-field duplicate structs, no untypedmap[string]anyescape hatches on shared types. - Strict Typing: use
provider.ContentTypeand the shared media-type helpers. No raw strings for modes. - Shared HTTP Client: use
internal/httpclient. Never instantiate a rawhttp.Client, except non-idempotent local calls (e.g. aria2 JSON-RPC) where retries could double-submit — see CODEBASE.md §12.
2. Refactor Logic (The "Must Needed" Flexibility)
Improvements are encouraged when they standardize inconsistency, remove redundancy, or improve cross-platform reliability — but verify the build after every change:
go vet ./... && go build ./... && staticcheck ./... && go test ./...
3. Communication Patterns
- When creating a new provider, explain the resolution strategy (e.g. "HTML scraping vs GraphQL").
- When modifying the TUI, ensure the corresponding behavior is expressed as a service/provider capability rather than new hardcoded branches.
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 · 78 lines · 717 tokens per session scan A 4c322da74298
kari AGENTS.md is an instructions file published in the GitHub repository Dhairya3391/kari (47 stars, last pushed today), licensed MIT. It adds 717 tokens to every session, about $0.0036 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.