Borrowing it
Nothing to install: this file belongs to Diadems666/unified-ai-cli-configurator. 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/Diadems666/unified-ai-cli-configurator/main/AGENTS.mdgit clone --depth 1 https://github.com/Diadems666/unified-ai-cli-configuratorWrote 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/diadems666/unified-ai-cli-configurator/agents-md)<a href="https://agentmods.dev/instructions/diadems666/unified-ai-cli-configurator/agents-md"><img src="https://agentmods.dev/badge/instructions/diadems666/unified-ai-cli-configurator/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/diadems666/unified-ai-cli-configurator/agents-md"><img src="https://agentmods.dev/badge/instructions/diadems666/unified-ai-cli-configurator/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00617 | $0.00617 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
unified-ai-cli-configurator 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 10d 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Renderer code lives in src/ with feature folders components/, pages/, store/, utils/, and types/. Electron main-process logic sits in electron/ (main.ts, preload.ts, detectors/, and config managers) and should mirror renderer types so IPC stays in sync. Tests reside in tests/, split into unit/ and integration/, using shared mocks from tests/setup.ts. Generated bundles (dist/, dist-electron/, release/) are disposable, while reference docs live in docs/.
Build, Test, and Development Commands
npm install— install dependencies.npm run dev— launch the Vite dev server on port 5173.npm run electron:dev— co-run the dev server and Electron shell for end-to-end testing.npm run build/npm run build:electron— generate web assets or Electron-ready output.npm run dist— build desktop installers intorelease/.npm run test,npm run test:run,npm run test:coverage— execute Vitest in watch, CI, or coverage modes.
Coding Style & Naming Conventions
The project uses strict TypeScript; keep nullability explicit and reuse contracts from @/types. Indent with 2 spaces, PascalCase components, camelCase functions and Zustand selectors, and reserve CONSTANT_CASE for shared constants. Favor the @/ alias over deep relative imports. Styling leans on Tailwind utilities declared in index.css, with custom CSS only when necessary. Define IPC contracts in electron/types.ts and surface them through the preload bridge.
Testing Guidelines
Vitest with vitest.config.ts and tests/setup.ts provides Electron API mocks. Keep renderer specs in tests/unit/*.test.ts and cross-process cases in tests/integration/*.test.ts, naming files <feature>.test.ts. Store fixtures under tests/__fixtures__/ and clean them after each test. Cover new features and IPC changes with unit tests, and run npm run test:coverage before submitting.
Commit & Pull Request Guidelines
Adhere to the established conventional commit style (feat:, fix:, docs:, etc.) visible in git log. Pull requests should describe user impact, link the tracking issue, and attach UI screenshots or GIFs when visuals change. Confirm npm run test (and any relevant build command) passes locally and call out follow-up tasks or known gaps in the PR body.
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.
- 10d ago First seen · 25 lines · 617 tokens per session scan A c4879c5fccc8
unified-ai-cli-configurator AGENTS.md is an instructions file published in the GitHub repository Diadems666/unified-ai-cli-configurator (2 stars, last pushed 11mo ago), licensed MIT. It adds 617 tokens to every session, about $0.0031 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-31.
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).
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.
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.