Borrowing it
Nothing to install: this file belongs to StoneSteel27/AutomatiQ. 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/StoneSteel27/AutomatiQ/main/AGENTS.mdgit clone --depth 1 https://github.com/StoneSteel27/AutomatiQWrote 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/stonesteel27/automatiq/agents-md)<a href="https://agentmods.dev/instructions/stonesteel27/automatiq/agents-md"><img src="https://agentmods.dev/badge/instructions/stonesteel27/automatiq/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.01302 | $0.01302 |
| Opus 5 | $0.00651 | $0.00651 |
| Sonnet 5 | $0.00260 | $0.00260 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
AutomatiQ 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines
Project Map
src/automatiq/mcp/- MCP server: FastMCP stdio server (server.py), runtime, annotation, logging_setup, vision, status_log. Every module stays under 700 lines.src/automatiq/core/- Recorder engine: config, events, cancel_standard, browser_manager, bin_manager, telemetry, andrecorder/(withcdp/,compile/,extension/subpackages).tests/- Pytest suite: 16 modules, 101 tests.- Legacy CLI (
record/run/agent/resume/feedback), LLM investigator agent, IPython sandbox, telemetry server backend, and banner scripts live only on thelegacy/v0.3.xbranch - do not port them back without explicit instruction.
Daily Commands
uv sync
uv run pytest -q
uv run ruff check src tests
- Use
uvstrictly. Do not usepiporpoetry. - Run tests regularly with
uv run pytest -q.
Doctrine
- Recorder changes are test-first. Fake CDP events fed to real handlers; new CDP event types, attributes, or output artifacts come with factories in
conftest.py, handler tests, and compile tests in the same change. - Tests never touch the network, a real browser, or a real LLM. Use fake CDP events and monkeypatch seams - e.g. patch
automatiq.mcp.runtime.vision_preflight- instead of live services. - The MCP surface stays five tools (start_recording, stop_recording, wait_for_completion, get_status, annotate_user_interactions). New capabilities extend existing tools or the per-session README, not MCP resources.
- Never log or echo
recorder_api_keyvalues. - Recordings under
automatiq_sessions/are unredacted secrets - never commit them. Same for.env.
Config
Precedence: AUTOMATIQ_* env > ~/.automatiq/config.toml > defaults.
Models: never hardcode model names. The model comes from [models] recorder config (a litellm string) only. The vision key comes ONLY from [models] recorder_api_key in ~/.automatiq/config.toml (keyless base_url local endpoints need none); provider env vars are never consulted as a key source and are overwritten by the config key when present; the key is read fresh per recording.
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 Changed · +4 lines · -367 tokens per session 08f9c24a1f44
- 7d ago First seen · 103 lines · 1,669 tokens per session scan A 6dd6affece36
AutomatiQ AGENTS.md is an instructions file published in the GitHub repository StoneSteel27/AutomatiQ (166 stars, last pushed 5d ago), licensed MIT. It adds 1,302 tokens to every session, about $0.0065 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
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.