Borrowing it
Nothing to install: this file belongs to baristaze/swe_guidelines. 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/baristaze/swe_guidelines/main/AGENTS.mdgit clone --depth 1 https://github.com/baristaze/swe_guidelinesWrote 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/baristaze/swe_guidelines/agents-md)<a href="https://agentmods.dev/instructions/baristaze/swe_guidelines/agents-md"><img src="https://agentmods.dev/badge/instructions/baristaze/swe_guidelines/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/baristaze/swe_guidelines/agents-md"><img src="https://agentmods.dev/badge/instructions/baristaze/swe_guidelines/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.02835 | $0.02835 |
| Opus 5.5 | $0.01134 | $0.01134 |
| Sonnet 5 | $0.00567 | $0.00567 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
swe_guidelines 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 today.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
This repository holds one guideline (architecture.md), a lens
catalog derived from it (lenses/), Claude Code skills that apply the
lenses (skills/), and the checkers that keep the three consistent
(scripts/, Makefile).
Layout
architecture.mdis the source of truth. Every rule in a lens or a skill restates a sentence in it; nothing adds a rule the guideline does not state.lenses/<group>.mdholds one group of lenses in the formatlenses/README.mddefines. Ids are<PREFIX>-NN; every lens citesSection titleorSection title, Subsection, by title and never by number.skills/arch-review-<group>/SKILL.mdis generated fromskills/_template/review.SKILL.md; edit the template and runmake gen-skills. The other skills are hand-written. The six scaffold skills shareskills/_shared/scaffold-conventions.md; the other hand-written skills do not.skills/_shared/ops-skills/holds the nine project-local operational skills as flat templates, one file each, withacmefor the product;arch-scaffold-newcopies them into a new tree, andmake leaks,make links, andmake linthold them. They are not skills of this plugin, but a new tree runs them as skills, soscripts/check_skills.pyreads their frontmatter and nothing else. It holds the same flatkey: valuelines a skill's frontmatter has. The name equals the file name. The description is one double-quoted string of at most 1024 characters, outside the plugin's description budget.allowed-toolsis comma-separated, with no bareBash, and each Bash entry is theBash(cmd:*)prefix form or an exactBash(make <target>).skills/arch-new-aspectis the one skill that edits this repository itself: it incorporates a new aspect into the guideline and cascades it through the lenses, skills, and docs, and names the release level.agents/arch-reviewer.mdis the subagentarch-review-fullfans out to. Its procedure and report shape mirror the review template, andscripts/check_agents.pyholds the two together: the four decision words, the report block, and the count of procedure steps must agree. The sentence "Never edit, stage, or commit" is repeated in every review skill on purpose..claude-plugin/holds the plugin and marketplace manifests. The repository root is the plugin.plugin.jsoncarries the one release version.scripts/check_version.pyholds every copy to it: the marketplace manifest, the changelog's latest release heading, the pinned tags inREADME.md,docs/adopting.md, andcheckers/README.md, and the arch-check package's version incheckers/pyproject.tomlandcheckers/src/arch_check/__init__.py.benchmark/holds the harness that measures a subject against a rubric (.github/workflows/benchmark.ymlruns every scenario on demand, never on push):run.pywith its inline dependencies, theharness/modules, the scenarios, the result schema, andserve.py. Every harness module imports the standard library only at import time, so the tests attests/test_benchmark_*.pyrun with nothing installed; the provider clients,pyyaml,jsonschema, andwebsocketsare imported inside the functions that use them. A run writes intobenchmark/runs/, which git ignores: the repository is the manual, a run is a measurement.make benchmarkruns the smoke scenario and is not part ofmake check, because a run calls paid APIs.checkers/holdsarch-check, the static checker that decides the mechanical lenses. It is its own Python package (checkers/src/arch_check/, Python 3.11, standard library only). A rule's id is the id of the lens it decides, and a rule is one module underrules/;checkers/README.mdsays how to add one.checkers/src/arch_check/lenses.pycarries every lens id and severity, andtests/test_arch_check_framework.pyholds it equal tolenses/*.md. The tests aretests/test_arch_check_*.py, on trees built withtests/arch_check_fixtures.py; they skip on Python 3.10.scripts/_common.pyholds what the scripts share, the heading anchor rule above all: the generator that writes anchors and the checker that resolves them use the same function. It also holds the one list of the repository's Markdown (markdown_files), which every script that scans Markdown reads, and the argument parser every script uses, and the one fence rule (fenced_lines) every script that skips code blocks uses.scripts/check_lenses.pyalso holds every identifier a lens quotes to the section the lens cites: a backticked name the guideline uses must appear in that section.CROSS_REFERENCESlists the few deliberate exceptions.tests/holds one pytest module per script, each on a small fixture tree, with a pass and a fail path per rule;make testruns them.
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.
- today Changed · +35 lines · +550 tokens per session ccb8b4819448
- yesterday Changed · +44 lines · +742 tokens per session 85d030ab22ba
- 2d ago First seen · 117 lines · 1,543 tokens per session scan A 13273a2629e7
swe_guidelines AGENTS.md is an instructions file published in the GitHub repository baristaze/swe_guidelines (86 stars, last pushed today), licensed MIT. It adds 2,835 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-09-20.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, repository design references, quickstart — add a new integration in 5 steps and integration architecture.
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.
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).