Borrowing it
Nothing to install: this file belongs to vamshi4001/saas-clawds. 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/vamshi4001/saas-clawds/main/AGENTS.mdgit clone --depth 1 https://github.com/vamshi4001/saas-clawdsWrote 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/vamshi4001/saas-clawds/agents-md)<a href="https://agentmods.dev/instructions/vamshi4001/saas-clawds/agents-md"><img src="https://agentmods.dev/badge/instructions/vamshi4001/saas-clawds/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/vamshi4001/saas-clawds/agents-md"><img src="https://agentmods.dev/badge/instructions/vamshi4001/saas-clawds/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.01368 | $0.01368 |
| Opus 5 | $0.00684 | $0.00684 |
| Sonnet 5 | $0.00274 | $0.00274 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
saas-clawds 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Instructions — SaaS Playbook
You are helping a founder build out their complete SaaS company operating system. This repository contains 26 departments with 130+ subfolders, each with an INSTRUCTIONS.md file that tells you what to create.
Your Mission
Help the founder populate every folder with actionable, specific documentation for their SaaS startup. You are not generating generic advice — you are creating their actual operating documents.
How to Work Through This Playbook
Step 1: Gather Context
Before populating any folders, you need to understand the founder's SaaS. Ask these questions if the answers aren't already provided:
- What is the name of your SaaS?
- Describe your product in 2-3 sentences. What does it do?
- Who is your target customer? (e.g., "small business owners", "enterprise DevOps teams", "freelance designers")
- What problem does it solve? (the specific pain point)
- How do you plan to make money? (subscription tiers, usage-based, freemium, etc.)
- What stage are you at? (idea, building MVP, launched, growing)
- What's your team size? (solo, 2-5, 5-20, 20+)
- What's your budget/runway? (bootstrapped, pre-seed, seed, Series A+)
Store the answers in company-profile.md at the root of this repository.
Step 2: Work Through Departments in Order
The departments are numbered 01-26 for a reason. Work through them sequentially:
01-idea → 02-validation → 03-planning → 04-design → 05-development →
06-infrastructure → 07-testing → 08-launch → 09-acquisition →
10-distribution → 11-conversion → 12-revenue → 13-analytics →
14-retention → 15-growth → 16-scaling →
17-legal → 18-finance → 19-sales → 20-customer-success →
21-product-management → 22-brand-and-positioning → 23-documentation →
24-competitive-intelligence → 25-data-and-ai → 26-people-and-culture
However, skip departments that aren't relevant to the founder's current stage. For example:
- If they're pre-launch, focus on 01-08, plus 17-legal, 18-finance, 22-brand
- If they're post-launch looking to grow, focus on 09-16 and 17-26
- If they need everything, go through all 26
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.
- 9d ago First seen · 130 lines · 1,368 tokens per session scan A e5f6f79e62a9
saas-clawds AGENTS.md is an instructions file published in the GitHub repository vamshi4001/saas-clawds (78 stars, last pushed 6mo ago), licensed MIT. It adds 1,368 tokens to every session, about $0.0068 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-30.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.