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/pydevices/pydevices-examples/agents-mdgit clone --depth 1 https://github.com/PyDevices/pydevices-examplesWrote 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/pydevices/pydevices-examples/agents-md)<a href="https://agentmods.dev/instructions/pydevices/pydevices-examples/agents-md"><img src="https://agentmods.dev/badge/instructions/pydevices/pydevices-examples/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.02720 | $0.02720 |
| Opus 5 | $0.01360 | $0.01360 |
| Sonnet 5 | $0.00544 | $0.00544 |
| Haiku 4.5 | $0.00272 | $0.00272 |
Grade A, and why
pydevices-examples 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 today.
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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cursor Cloud specific instructions
This repo is a showcase: examples and a PyScript gallery for the PyDevices
driver stack, not the product itself. The shareable product libraries and their
docs live in sibling pydevices. There is no build step for examples.
.site/pyscript/lib is a symlink to ../../lib, so editing lib/ updates the
PyScript gallery too.
Docs map (this repo's docs/ is small on purpose — see
docs/README.md): docs/peterhinch-guis.md
(Nano-GUI / Micro-GUI / MicroPython-Touch), docs/tft-gui.md
(@russhughes TFT GUI stub), docs/screenshots/.
Code-adjacent runbooks: tools/README.md (example test
matrix, PyScript/Playwright debugging, LVGL timer harnesses),
lib/utils/README.md, scripts/README.md,
tests/README.md.
Environment
displaydev, audiodev, optional appdev, multimer, events, keys,
and portable hardware utilities live in sibling
pydevices, which
also owns TestPyPI/MIP publishing. Non-LVGL examples instantiate
appdev.App(board_config); LVGL examples import it from display_driver.
Board configs never own an appdev.App. AutoDisplay is imported from
displaydev.auto only.
- Cursor Cloud (multi-repo workspace): do not use a local
.cursor/environment.jsonin this repo. The canonical cloud environment lives in PyDevices/.github — start Cloud Agents from that repo (orcmods) with the saved Pydevices Cloud Workspace environment. Its install command isbash scripts/cloud-workspace-install.sh(relative to the.githubcheckout), which symlinks/agent/repos/*into~/gh/pydevices/. See AGENTS.md there. - Use the repo-root virtualenv at
.venvfor all Python tooling (.venv/bin/python,.venv/bin/ruff,.venv/bin/pytest). The systempython3has no project dependencies installed. - Browser testing with Playwright: see
.agents/rules/playwright_environment_rule.md. - Desktop matrices use repo
.venv(cpython-venv) plus interpreters onPATH(micropython,circuitpython, and when presentmicropython.exe/python.exe).jupyter.py(frompydevices/bin),./scripts/pyscript.sh, andandroid.py(frompydevices/bin, onPATH) aid Jupyter, PyScript, and Android (adb stage ontoorg.pydevices.runner; cwd paths like CLI Python — not PyScript gallery). Opt-in matrix:tools/example_test_kit.py --only-interpreter android …. - The desktop display backend on CPython on Windows is
PGDisplay(pygame-ce;import pygame). Preferpython.exefor PG work. Do not install pygame-ce into.venv/ systempython3on this laptop — those stay SDL-primary;board_configfalls back toSDLDisplaywhen pygame-ce's publicpygame.WindowAPI is missing.pygame-ceis intentionally not inrequirements-dev.txt.
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.
- today Changed · -4 tokens per session 0b1477dfce70
- 4d ago First seen · 179 lines · 2,724 tokens per session scan A a0de6313da55
pydevices-examples AGENTS.md is an instructions file published in the GitHub repository PyDevices/pydevices-examples (52 stars, last pushed yesterday), licensed MIT. It adds 2,720 tokens to every session, about $0.0136 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.
Other instructions, from other repositories
vibepulse AGENTS.md
Instructions for niclasvestlund-YT/vibepulse, covering vibepulse — firmware för hyllskärmen, status (2026-08-28, v1.0.0), arbetsregler, releaser och utåtriktad dokumentation and amoled visual work.
vibepulse CLAUDE.md
Instructions for niclasvestlund-YT/vibepulse, covering over-the-air updates, amoled visual work, logs, errors, and learning from mistakes, hardware-aware work and releases and the readme.
uad-console-mcp AGENTS.md
AGENTS.md instructions for fomoPhil/uad-console-mcp, covering agents.md, orientation, hard rules, canonical flows and label an adat expander.
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
cad-cae-copilot copilot-instructions.md
Copilot instructions for armpro24-blip/cad-cae-copilot, covering github copilot — aieng workspace and essentials.