Borrowing it
Nothing to install: this file belongs to entropy-cloud/attractor-guided-engineering-template. 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/entropy-cloud/attractor-guided-engineering-template/main/AGENTS.mdgit clone --depth 1 https://github.com/entropy-cloud/attractor-guided-engineering-templateWrote 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/entropy-cloud/attractor-guided-engineering-template/agents-md)<a href="https://agentmods.dev/instructions/entropy-cloud/attractor-guided-engineering-template/agents-md"><img src="https://agentmods.dev/badge/instructions/entropy-cloud/attractor-guided-engineering-template/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/entropy-cloud/attractor-guided-engineering-template/agents-md"><img src="https://agentmods.dev/badge/instructions/entropy-cloud/attractor-guided-engineering-template/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02830 | $0.02830 |
| Opus 5.5 | $0.01132 | $0.01132 |
| Sonnet 5.5 | $0.00566 | $0.00566 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
attractor-guided-engineering-template 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Intent
mission-driver (self-hosting AGE workspace) uses a lightweight Attractor-Guided Engineering workflow for AI-assisted application development.
This repository is for an application-layer product, not a framework-core project.
The repo is the source of truth. Chat is only a temporary working surface.
Dual-Audience Repo
This repository serves two audiences:
- As a real project — it develops
tools/mission-driver/(a Node.js Flow DSL engine + Vue 3 monitor dashboard) using its own AGE workflow. The repo dogfoods its own methodology. - As a template — consumers run
./install-age.sh /path/to/target "Project Name"from a clone of this repo. The installer copies a curated file set listed ininstall-age.manifest(sourcing fill-in files fromtemplate/and shared methodology guides from repo root) into a new project root, then auto-creates the mission-driver shim,.env,missions/base.json,docs/logs/{year}/, and.gitignore.
Files at the repo root and under docs/ are the REAL PROJECT versions (filled in for mission-driver development). Pristine template versions of fill-in files live under template/. For the manual fallback flow (no bash), see template/START-HERE-after-copy.md; for the primary automated flow, run ./install-age.sh and read its NEXT STEPS output.
In-Tree Tool
tools/mission-driver/ is a real, in-tree Node.js tool — NOT a scaffold example. It is the engine that automates this repo's own AGE loop. Read tools/mission-driver/CONTEXT.md for the 30-second overview. It is attached as subdirectory context when you read files under tools/mission-driver/.
Before writing non-trivial code, agents must first understand:
docs/context/project-context.mddocs/context/ai-autonomy-policy.mddocs/context/codebase-map.md- the requirement or owner doc (under
docs/requirements/ordocs/design/) that describes the work's intended behavior — current work-in-progress is read from unfinished plans indocs/plans/, not from a field inproject-context.md - the relevant raw inputs under
docs/input/when requirement meaning depends on source material
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.
- 1mo ago First seen · 191 lines · 2,830 tokens per session scan A 02c835474450
attractor-guided-engineering-template AGENTS.md is an instructions file published in the GitHub repository entropy-cloud/attractor-guided-engineering-template (81 stars, last pushed 1mo ago), licensed MIT. It adds 2,830 tokens to every session, about $0.0113 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.