Borrowing it
Nothing to install: this file belongs to DasDarki/PixelLabRat. 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/DasDarki/PixelLabRat/master/AGENTS.mdgit clone --depth 1 https://github.com/DasDarki/PixelLabRatWrote 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/dasdarki/pixellabrat/agents-md)<a href="https://agentmods.dev/instructions/dasdarki/pixellabrat/agents-md"><img src="https://agentmods.dev/badge/instructions/dasdarki/pixellabrat/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.00859 | $0.00859 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
PixelLabRat 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 6d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on PixelLabRat
Guidance for AI agents (and humans) contributing to this repo. If you only want to use PixelLabRat to generate art from Claude Code, read docs/using-with-claude-code.md instead.
Layout
A Bun workspace. TypeScript everywhere.
packages/
core/ PixelLab API client + typed wrapper, auth, async job polling
store/ project store (folders + JSON), the style contract, generation logic
mcp/ the MCP server (Claude Code / any MCP client)
agent/ the embedded Claude agent — tool defs + system prompt
app/ Electron + Vue 3 desktop frontend
A project is a folder, not a database row: a manifest, a few JSON files
(library.json, characters.json, …), and the PNGs. The store reads and writes
those directly.
Commands
bun run typecheck # core/store/mcp/agent
cd packages/app && bun run typecheck # the app (vue-tsc) — run separately
bun run store:check # store round-trip, offline
bun run mcp:check # MCP round-trip, offline
bun run agent:check # agent tools + prompt, offline
bun run app:dev / app:build # the desktop app
The *:check scripts and the typechecks are offline and free — use them. Do
not call the real PixelLab API in tests; generations cost money. bun run smoke (balance only) is the cheapest live sanity check.
Adding a PixelLab capability
Generation features flow through the layers in this order, and the agent and MCP surfaces are kept at parity:
- core (
packages/core/src/pixellab.ts) — add the method (submit + poll for async jobs, or a direct call for sync ones). - store (
packages/store/src/generate.ts) — add the project-aware function that applies the style contract and persists results viaproject.ts. - agent (
packages/agent/src/tools.ts) and mcp (packages/mcp/src/server.ts) — expose it as a tool in both. They should stay in sync; if you add a tool to one, add it to the other. - app — thread it through
shared/api.ts→main/ipc.ts→preload/index.ts→renderer/store.ts→ the relevant component.
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.
- 6d ago First seen · 76 lines · 859 tokens per session scan A e840450e3082
PixelLabRat AGENTS.md is an instructions file published in the GitHub repository DasDarki/PixelLabRat (0 stars, last pushed 2mo ago), licensed MIT. It adds 859 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-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).
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.