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.
npx agentmods add instructions/aimny2020/agentpalette/agents-mdgit clone --depth 1 https://github.com/Aimny2020/agentpaletteWrote 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/aimny2020/agentpalette/agents-md)<a href="https://agentmods.dev/instructions/aimny2020/agentpalette/agents-md"><img src="https://agentmods.dev/badge/instructions/aimny2020/agentpalette/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 | $0.00580 | $0.00580 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
agentpalette 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.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
AgentPalette is a Tauri v2 desktop application. React and TypeScript live in src/: app/ owns routing, providers, and the shared shell; features/ contains page-level modules; shared/ contains IPC clients, reusable UI, theme state, styles, and mock data. Rust lives in src-tauri/src/: commands/ exposes thin Tauri handlers, application/ coordinates use cases, domain/ defines stable models and ports, and infrastructure/ implements SQLite and platform adapters. Database migrations are in src-tauri/migrations/. Product specifications and plans are under docs/superpowers/.
Build, Test, and Development Commands
npm installinstalls frontend and Tauri CLI dependencies.npm run tauri:devlaunches the complete desktop application.npm run devruns only the Vite frontend at127.0.0.1:1420.npm run buildtype-checks TypeScript and creates the production frontend bundle.npm run test:runruns Vitest once; usenpm testfor watch mode.cargo test --manifest-path src-tauri/Cargo.tomlruns Rust tests.cargo clippy --manifest-path src-tauri/Cargo.toml -- -D warningsenforces warning-free Rust.
Coding Style & Naming Conventions
Use two-space indentation in TypeScript and four spaces in Rust. React components and files use PascalCase; hooks and utilities use camelCase; Rust modules and functions use snake_case. Keep Tauri commands small and move decisions into application/domain code. Format Rust with cargo fmt; TypeScript must pass npm run lint. Prefer semantic CSS classes and variables from src/shared/styles/tokens.css.
Testing Guidelines
Follow red-green-refactor. Place frontend tests beside code as *.test.ts(x) and Rust unit tests in the relevant module. Test user-visible behavior with Testing Library and isolate only native Tauri boundaries. New IPC types, domain rules, routes, and error mappings require tests. Run both test suites before requesting review.
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.
- 3d ago First seen · 32 lines · 580 tokens per session scan A e0239859d99b
agentpalette AGENTS.md is an instructions file published in the GitHub repository Aimny2020/agentpalette (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 580 tokens to every session, about $0.0029 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
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
superpowers-reasonix AGENTS.md
Instructions for christopherarter/superpowers-reasonix, covering project guidance, skills — stop. load a skill before you act, red flags — these thoughts mean stop. you are rationalizing and priority.
ai-mind AGENTS.md
AGENTS.md instructions for HWYD/ai-mind, covering agents, version spec workspace continuity (mandatory), 项目定位, 事实来源优先级 and 开始大改前先读什么.
vvvv-skills CLAUDE.md
Claude Code instructions for tebjan/vvvv-skills, covering vvvv gamma, when to patch vs code, core concepts, live environment and important conventions.
pi AGENTS.md
AGENTS.md instructions for counterposition/pi, covering agents.md, commands, pattern: pnpm --filter @counterposition/pi-web-search run, single test file and single test by name.
SciCrucible CLAUDE.md
Claude Code instructions for Xinyang-Li666/SciCrucible, covering 科学知识库, 知识库结构, 可用命令, 项目目录 and 工作原则.