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/gladysassistant/gladys/agents-mdgit clone --depth 1 https://github.com/GladysAssistant/GladysWrote 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/gladysassistant/gladys/agents-md)<a href="https://agentmods.dev/instructions/gladysassistant/gladys/agents-md"><img src="https://agentmods.dev/badge/instructions/gladysassistant/gladys/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.02456 | $0.02456 |
| Opus 5 | $0.01228 | $0.01228 |
| Sonnet 5 | $0.00491 | $0.00491 |
| Haiku 4.5 | $0.00246 | $0.00246 |
Grade A, and why
Gladys 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cursor Cloud specific instructions
Gladys Assistant is a privacy-first smart home platform. The repo has two dev services:
- server (
/server): Node.js + Express REST/WebSocket API on port 1443, using SQLite + DuckDB for storage. Started withnodemon(hot reload). - front (
/front): Preact SPA (via Vite) on port 1444, API athttp://localhost:1443.
The root package.json orchestrates both via npm-run-all.
Running the app (dev mode)
From the repo root: npm start (runs run-p start-server:dev start-front:dev). The server listens on http://localhost:1443 and the front dev server on http://localhost:1444. Open the front URL; on a fresh DB it starts the onboarding/signup flow (create first admin account → preferences → house/room → dashboard). The server auto-creates/migrates its SQLite DB (server/gladys-development.db) on start, so no manual migration is needed for a fresh dev run.
Non-obvious caveats
- Harmless startup errors: on
npm startyou'll see smart-home device discovery errors (e.g.SonosDiscoveryError: No players found) because no physical devices exist in the VM/network. These are expected and do not affect the app. - Service dependencies: the server has ~38 integration services under
server/services/*, each with its ownpackage.json.cd server && npm installruns apostinstall(cli/install_service_dependencies.js) that installs deps for every service. SetINSTALL_SERVICES_SILENT_FAIL=trueso a single flaky service install does not abort the whole install. - Native modules (
sqlite3,bcrypt,sharp, USB/bluetooth services) compile from source; they need build tools (gcc/g++/make/python3) andlibudev-devon the system. DuckDB (@duckdb/node-api) ships prebuilt platform binaries and does not compile from source.
Feature specs (spec-first process)
Living specifications live in docs/specs/. They are the source of truth for the behavior and cross-repo contracts of the features they cover.
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.
- 4d ago First seen · 127 lines · 2,456 tokens per session scan A 7e90a3255977
Gladys AGENTS.md is an instructions file published in the GitHub repository GladysAssistant/Gladys (3,174 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,456 tokens to every session, about $0.0123 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
core integrations.instructions.md
Instructions for home-assistant/core, covering file locations, general guidelines, entity platforms, integration quality scale and how rules apply.
core copilot-instructions.md
Copilot instructions for home-assistant/core, covering copilot code review instructions, pull request template, breaking change, proposed change and type of change.
core CLAUDE.md
Claude Code instructions for home-assistant/core, a project described as: :housewithgarden: Open source home automation that puts local control and privacy first.
core AGENTS.md
AGENTS.md instructions for home-assistant/core, covering github copilot & claude code instructions, git commit guidelines, pull requests, development commands and python syntax notes.
devices-mcp AGENTS.md
Instructions for sandraschi/devices-mcp, covering devices-mcp — per-repo agent instructions, what this repo is, git branches, startup and backend only (fastapi, port 10717).
devices-mcp CLAUDE.md
Instructions for sandraschi/devices-mcp, covering devices-mcp -- claude code guide, entry points, standards and ports.