Borrowing it
Nothing to install: this file belongs to bricerising/enterprise-software-playbook. 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/bricerising/enterprise-software-playbook/main/AGENTS.mdgit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/agents-md)<a href="https://agentmods.dev/instructions/bricerising/enterprise-software-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/bricerising/enterprise-software-playbook/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.00445 | $0.00445 |
| Opus 5 | $0.00222 | $0.00222 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
enterprise-software-playbook 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.
What it actually says
Agent Instructions (enterprise-software-playbook)
This repo is itself an opinionated system for writing agent skills. To prevent drift, follow the repo specs.
Repo Structure
skills/— one directory per skill, each containingSKILL.md(frontmatter + body) and optionalreferences/specs/— specifications, decision records (specs/decisions/), templates, andskills-manifest.jsontools/— bundled tool implementations (e.g.,tools/archobs/,tools/intelligence/), each a self-contained project.system/— internal tooling: skill creator scripts, doc generation, CI templates
Start Here
- Read
specs/000-index.md(index) andspecs/004-change-process.md(how to make changes). - Taxonomy and default workflow live in
specs/003-taxonomy-and-workflow.md.
Change Rules (High Signal)
- Treat skill names as API: prefer stable names; if you rename, capture it in a decision record and update docs (
specs/002-skill-contract.md). - For non-trivial changes, add/update a decision record in
specs/decisions/. - Keep skills concise; put depth in
references/(progressive disclosure). - Prefer cross-links between skills over duplicating content.
- Keep
specs/skills-manifest.jsonaligned with each skill's frontmatter metadata (stage, tags) and maintain manifest-only fields (trigger, related, overhead).
Verification
- Validate changed skills:
python3 .system/skill-creator/scripts/quick_validate.py skills/<skill-folder> - Validate repo-level docs/workflow consistency:
python3 .system/skill-creator/scripts/check_repo_consistency.py - Keep
README.mdandPROMPTS.mdaligned with the workflow-stage grouping (Define/Standardize/Harden/Verify).
Packaging (Optional)
- Package skills to
dist/(build output):python3 .system/skill-creator/scripts/package_skill.py skills/<skill-folder> ./dist
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 · 34 lines · 445 tokens per session scan A 651eb29c4571
enterprise-software-playbook AGENTS.md is an instructions file published in the GitHub repository bricerising/enterprise-software-playbook (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 445 tokens to every session, about $0.0022 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
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.