Borrowing it
Nothing to install: this file belongs to jmagly/aiwg. 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/jmagly/aiwg/main/AGENTS.mdgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/agents-md)<a href="https://agentmods.dev/instructions/jmagly/aiwg/agents-md"><img src="https://agentmods.dev/badge/instructions/jmagly/aiwg/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/jmagly/aiwg/agents-md"><img src="https://agentmods.dev/badge/instructions/jmagly/aiwg/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.00579 | $0.00579 |
| Opus 5.5 | $0.00232 | $0.00232 |
| Sonnet 5.5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
aiwg 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hound-mcp AGENTS.md — 100% identical, 33 lines differ
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Provider workspace bootstrap
Read and follow WORKSPACE.md first. Then read AIWG.md for AIWG discovery, quickrefs, and framework routing.
These are explicit reading instructions. Plain Markdown links are not claimed to auto-load.
Framework Context
See AIWG.md for the full AIWG framework context (active frameworks, addons, agents, behaviors, rules). Tracker and delivery source of truth: .aiwg/aiwg.config.
Deployed artifacts live under your provider's native directory
(for example .codex/agents/, .warp/agents/, .github/agents/).
Use aiwg discover "<intent>" and aiwg show <type> <name> to browse
skills, agents, rules, and commands across the installation.
See AGENTS.override.md for operator-authored additions.
AGENTS.md — Grok Build + AIWG
This project uses AIWG with the experimental grok-build provider.
Discover AIWG capabilities
export PATH="$(npm prefix -g)/bin:$PATH"
aiwg discover "<need>"
aiwg show skill <name>
Grok Build loads this file (and nested AGENTS.md / .grok/rules/*.md)
hierarchically from the repo root to the working directory; deeper files win on
conflicts. Prefer explicit aiwg discover / aiwg show for the full framework
corpus beyond the deployed kernel skills.
Native paths
- Project kernel skills:
.grok/skills/(standard skills stay index-driven unless--copy-all) - Startup / context:
AGENTS.mdand host-discovered.grok/rules/*.md(AIWG rule writer remains indexed) - Config only (not startup context):
.grok/config.toml - User home:
$GROK_HOME(default~/.grok) — skills under$GROK_HOME/skills/
AIWG emits the qualified reasoning, coding, and efficiency model-worker agents under .grok/agents/.
Other AIWG agents remain discoverable through aiwg discover and aiwg show agent until their native mappings are qualified.
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 Changed · +33 lines · +337 tokens per session 8afaac563ae3
- 1mo ago First seen · 30 lines · 242 tokens per session scan A 9a7a375b6450
aiwg AGENTS.md is an instructions file published in the GitHub repository jmagly/aiwg (224 stars, last pushed today), licensed MIT. It adds 579 tokens to every session, about $0.0023 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.