deepchat AGENTS.md

Repository instructions for DeepChat, an Electron and Vue desktop assistant that connects AI to personal information. They describe the code layout, package-manager requirements, and testing approach.

In plain words
What is it for?
Editing the desktop app, choosing the right test suite, running checks with pnpm, and protecting important user-facing behavior or regressions.
Why use it?
They help the coding agent make small, compatible changes without adding unnecessary dependencies or tests tied only to implementation details.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/thinkinaixyz/deepchat/agents-md
Clone the repo
git clone --depth 1 https://github.com/ThinkInAIXYZ/deepchat

Made for: Codex, OpenCode.

Per session 443 This file is loaded in full into every session.
When invoked 443 The same file β€” it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00443 $0.00443
Opus 5 $0.00221 $0.00221
Sonnet 5 $0.00089 $0.00089
Haiku 4.5 $0.00044 $0.00044

Measured 3d ago against content hash 80c4bfe06348, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deepchat 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 3d 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.

AGENTS.md Β· 27 lines

What it actually says

Repository Guidelines

  • Prefer the smallest correct change; add no abstraction or dependency without a real need.
  • Preserve unrelated worktree changes; avoid destructive Git unless explicitly requested.
  • Use pnpm only; require Node >=20.19 and pnpm >=10.11.
  • Core code: src/main, src/preload, src/renderer, src/shared; stack: Electron/Vue 3/TS.
  • Tests: use Vitest in test/main, Vitest with Vue Test Utils in test/renderer, and Playwright in test/e2e; run the smallest relevant suite.
  • Default to implementation-first development: inspect and design, complete the planned code change, then decide what new verification is needed. Do not default to TDD unless explicitly requested or a minimal executable reproduction is required to understand a complex failure.
  • Existing checks may run at any time. Treat new tests as regression protection, not implementation scaffolding; remove temporary probes and tests before handoff.
  • Commit only the smallest durable tests for user-visible behavior, documented contracts, persistence or migration, lifecycle or concurrency, recovery, security boundaries, or proven regressions. Prefer no new test to implementation-coupled coverage.
  • Keep native capabilities behind typed preload/IPC boundaries with context isolation enabled.
  • Use vue-i18n for user copy; prefer existing shadcn-vue primitives and VueUse utilities.
  • Follow Oxfmt: single quotes, no semicolons, 100 columns.
  • Before editing, inspect ownership, callers, tests, and nearby patterns; fix the root cause.
  • Before handoff run format, i18n, lint, typecheck, and relevant test suites.
  • Keep provider and ACP registry refreshes produced by normal builds.
  • Use Conventional Commits (type(scope): subject, <=50 chars); never add AI co-authors.
  • Target routine PRs to dev; only release branches target main.
  • Assess scope first; use SDD only for large features or complex changes, never small local work.
  • For UI changes, include concise BEFORE/AFTER ASCII layouts in the PR.
Changes

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.

  1. 3d ago First seen Β· 27 lines Β· 443 tokens per session scan A 80c4bfe06348

Subscribe to this mod's changes

deepchat AGENTS.md is an instructions file published in the GitHub repository ThinkInAIXYZ/deepchat (6,302 stars, last pushed yesterday), licensed Apache-2.0. It adds 443 tokens to every session, about $0.0022 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.

Related

Other instructions, from other repositories