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/asamiile/logic-lab/agents-mdgit clone --depth 1 https://github.com/asamiile/logic-labWhat 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.00724 | $0.00724 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
logic-lab 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for Logic Lab
Commit Policy
Do not commit changes to git. The user handles all commits manually.
Agents may edit files, create directories, and run checks, but must not run git add, git commit, or other git write operations.
Implementation Preferences
- Implement straightforward tasks directly.
- Keep changes scoped to the requested domain or tool.
- Run syntax checks for changed Python files.
- Run focused tests or smoke checks when practical.
- Leave the working tree ready for user review.
Project Structure
Logic Lab contains Python and py5 translations and experiments for creative coding algorithms.
Use domain-based organization:
physics/for motion, forces, particles, waves, oscillation, and physical systems.steering_behaviors/for autonomous agents, path following, flow fields, sensors, and swarms.genetic_algorithms/for DNA, mutation, selection, and evolutionary search.neuro_evolution/for neural networks evolved by genetic algorithms.fractals/for recursion, L-systems, trees, Koch curves, and spatial subdivision.cellular_automata/for CA grids, lattice rules, Pascal patterns, and emergence.mathematical/for mathematical geometry and numerical generative systems.tiling_patterns/for symmetry, tiling, textile, and deformation systems.research/for experimental or hybrid systems that do not fit cleanly elsewhere.shared/for reusable libraries used by multiple sketches.
Each simulation should usually follow:
domain/simulation_name/
├── simulation_name.py
├── README.md
└── screenshots/
MCP And Manifest
Logic Lab exposes selected algorithm knowledge through a local read-only MCP server in mcp/logic_lab_server.py.
The search index lives at .agents/art_manifest.json. When adding a new algorithm or simulation, agents should:
-
Add or update the simulation code and
README.md. -
Run:
uv run python .agents/update_art_manifest.py --write
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.
- yesterday First seen · 82 lines · 724 tokens per session scan A 12e349e63dba
logic-lab AGENTS.md is an instructions file published in the GitHub repository asamiile/logic-lab (0 stars, last pushed 5d ago), licensed MIT. It adds 724 tokens to every session, about $0.0036 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
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.