Borrowing it
Nothing to install: this file belongs to ulises-jeremias/agentic-workstation. 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/ulises-jeremias/agentic-workstation/main/AGENTS.mdgit clone --depth 1 https://github.com/ulises-jeremias/agentic-workstationWrote 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/ulises-jeremias/agentic-workstation/agents-md)<a href="https://agentmods.dev/instructions/ulises-jeremias/agentic-workstation/agents-md"><img src="https://agentmods.dev/badge/instructions/ulises-jeremias/agentic-workstation/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.01506 | $0.01506 |
| Opus 5 | $0.00753 | $0.00753 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
agentic-workstation 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 7d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines for agentic-workstation
For AI coding assistants and automation agents. Last Updated: 2026-03-16
Purpose
This repository provides a reusable chezmoi-based agentic-workstation baseline for agentic-workstation.
agentic-workstation's role is thin-host machine provisioning: chezmoi, shell tools, packages, LLM policy, tmux/Herdr, and Toolkit installation (via dots-skills install-toolkit). Workstation installs tools, Toolkit owns orchestration (swarm recipes, loops, generic queue). Skills, agent personas, and profiles are distributed by agent-toolkit — a separate repository installed automatically during chezmoi apply. dots-skills delegates to agent-toolkit for skill sync; dots-loop wraps agent-toolkit loop; dots-devcompanion runner + policy stays host-specific in Workstation (LLM policy, env.d), while agent-toolkit devcompanion owns generic queue behavior.
The bundled agentic-workstation-assistant skill is the agentic-workstation Assistant: use it in any repository (including client work), not only this checkout. It instructs agents to inspect project documentation in a fixed order (README → docs/ → AGENTS.md → CONTRIBUTING → PR templates → official scripts → devcontainer → CI → configs → code), to cite sources, and to treat AGENTS.md as the primary agent contract when present. On this repo it also uses docs/ and dots-*; elsewhere it still applies the same repo-inspection model plus machine-local agentic-workstation tooling when relevant.
Core Principles
- Keep the baseline simple and extensible.
- Never commit secrets, tokens, or private credentials.
- Prefer profile-driven configuration over host-specific logic.
- Keep scripts idempotent and safe to re-run.
- Treat documentation as part of the product.
Script Standards
All shell scripts must:
- use
set -eo pipefail - avoid destructive behavior by default
- detect OS before package manager operations
- skip already-installed tools
- print clear human-readable error messages
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.
- 7d ago First seen · 109 lines · 1,506 tokens per session scan A 41eb8345d200
agentic-workstation AGENTS.md is an instructions file published in the GitHub repository ulises-jeremias/agentic-workstation (2 stars, last pushed 4d ago), licensed MIT. It adds 1,506 tokens to every session, about $0.0075 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
multiagent-template copilot-instructions.md
Instructions for Neftedollar/multiagent-template, covering workspace structure, how to work in this repo, multi-agent pipeline, orchestrator role and escalate to human only for.
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).
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.
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).