Borrowing it
Nothing to install: this file belongs to shwilliamson/automatasaurus. 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/shwilliamson/automatasaurus/main/CLAUDE.mdgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/claude-md)<a href="https://agentmods.dev/instructions/shwilliamson/automatasaurus/claude-md"><img src="https://agentmods.dev/badge/instructions/shwilliamson/automatasaurus/claude-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.01391 | $0.01391 |
| Opus 5 | $0.00696 | $0.00696 |
| Sonnet 5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
automatasaurus CLAUDE.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 6d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automatasaurus Development Guide
Automatasaurus is a workflow orchestration framework for Claude Code that enables multi-agent autonomous development through GitHub issues and PRs.
Project Structure
automatasaurus/
├── bin/cli.js # CLI entry point (init, update, status)
├── src/
│ ├── commands/ # CLI command implementations
│ │ ├── init.js # Initialize framework in target project
│ │ ├── update.js # Update framework to latest version
│ │ └── status.js # Show installation status
│ └── lib/ # Shared utilities
│ ├── paths.js # Path utilities (template dir, project dir)
│ ├── manifest.js # Track installation state (.automatasaurus/.manifest.json)
│ ├── symlinks.js # Create .claude -> .automatasaurus symlinks
│ ├── block-merge.js # Merge content into marked blocks in files
│ └── json-merge.js # Deep merge JSON settings
├── template/ # Files installed into target projects
│ ├── CLAUDE.block.md # Core framework docs (block-merged)
│ ├── commands.block.md # Framework commands (block-merged)
│ ├── settings.json # Claude Code settings with hooks
│ ├── mcp.json # MCP server config (Playwright)
│ ├── commands/ # Slash command definitions
│ ├── agents/ # Specialized personas (PM, Developer, Architect, etc.)
│ ├── skills/ # Reusable knowledge modules
│ └── hooks/ # Shell scripts (notify, on-stop, request-attention)
└── .claude/ # Symlinked to template/ for dogfooding
Commands
npm test # Run tests (node --test src/**/*.test.js)
npx automatasaurus init # Test installer on a project
npx automatasaurus update # Test update mechanism
npx automatasaurus status # Test status display
Key Concepts
Block Merging
Files with .block.md extension use marked blocks that get merged into target files:
<!-- AUTOMATASAURUS:START -->
Framework content here (replaced on update)
<!-- AUTOMATASAURUS:END -->
Content outside blocks is preserved during updates.
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.
- 6d ago First seen · 162 lines · 1,391 tokens per session scan A f86c7cfbd52a
automatasaurus CLAUDE.md is an instructions file published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 1,391 tokens to every session, about $0.0070 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.