Borrowing it
Nothing to install: this file belongs to praveenjuge/teak. 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/praveenjuge/teak/main/AGENTS.mdgit clone --depth 1 https://github.com/praveenjuge/teakWrote 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/praveenjuge/teak/agents-md)<a href="https://agentmods.dev/instructions/praveenjuge/teak/agents-md"><img src="https://agentmods.dev/badge/instructions/praveenjuge/teak/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.00854 | $0.00854 |
| Opus 5 | $0.00427 | $0.00427 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
teak 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teak agent guide
Teak is a personal knowledge hub for collecting, remembering, and rediscovering ideas and inspiration.
Start here
- Use Bun. Read the pinned version and available commands from
package.json; do not duplicate that inventory here. - Read the nearest nested
AGENTS.mdbefore changing a workspace. - Inspect the current implementation and tests before choosing a pattern. Treat repository code and configuration as the source of truth.
- Keep changes focused. Preserve unrelated work already in the tree.
Architecture invariants
- This is a Turborepo monorepo. Applications live in
apps/*; shared backend and UI code live inpackages/convexandpackages/ui. - Client reads use the cached Convex query hooks. Writes use Convex mutations or actions. Better Auth sessions provide Convex identity.
- Import backend APIs from
@teak/convex, generated data types from@teak/convex/_generated/dataModel, and shared constants from@teak/convex/shared/constants. - Shared web, desktop, and extension UI belongs in
packages/uiunless the behavior is surface-specific. - Card processing is orchestrated by
packages/convex/workflows/cardProcessing.ts. Preserve workflow retries andprocessingStatusconsistency. - Supported card types are text, link, image, video, audio, document, palette, and quote.
Convex work
Before editing anything under packages/convex, read packages/convex/_generated/ai/guidelines.md completely. Its generated Convex rules override general guidance.
Schema changes require explicit approval for any migration or backfill. Define indexes in packages/convex/schema.ts and scheduled jobs in packages/convex/crons.ts.
Verification
- Add or update deterministic tests for changed behavior. Run the narrowest relevant checks first, then the repository checks warranted by the change.
- Test user-observable behavior rather than implementation details.
- Cross-surface production journeys belong in
packages/tests; readpackages/tests/README.mdbefore changing or running them. - Never bypass git hooks with
--no-verify. Fix the failing check. - Verify user-facing work in the real interface when practical. A passing build alone is not proof of the experience.
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 · 62 lines · 854 tokens per session scan A 113c7acd55f4
teak AGENTS.md is an instructions file published in the GitHub repository praveenjuge/teak (25 stars, last pushed today), licensed MIT. It adds 854 tokens to every session, about $0.0043 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.