What is saaskit AGENTS.md?

A project instruction file for working on the saaskit codebase. It explains how to track tasks, finish coding sessions, and send completed changes to the shared repository.

Use it to find available work, update and close issues, run checks after code changes, synchronize task data, and push finished work.

It gives coding agents a fixed process, so unfinished tasks, missing checks, and unshared local changes are less likely to be overlooked.

saaskit AGENTS.md — Instructions file by saas-studio

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add instructions/saas-studio/saaskit/agents-md

Clone the repo

git clone --depth 1 https://github.com/saas-studio/saaskit

Made for: Codex, OpenCode.

Per session 333 This file is loaded in full into every session.

When invoked 333 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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	$0.00333	$0.00333
Opus 5	$0.00167	$0.00167
Sonnet 5	$0.00067	$0.00067
Haiku 4.5	$0.00033	$0.00033

Measured 2d ago against content hash bf83e48f5820, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

saaskit 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 2d 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.

Origin

This is a copy

100% identical to dspy-skills AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 41 lines

What it actually says

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

File issues for remaining work - Create issues for anything that needs follow-up
Run quality gates (if code changed) - Tests, linters, builds
Update issue status - Close finished work, update in-progress items

PUSH TO REMOTE - This is MANDATORY:

git pull --rebase
bd sync
git push
git status  # MUST show "up to date with origin"

Clean up - Clear stashes, prune remote branches
Verify - All changes committed AND pushed
Hand off - Provide context for next session

CRITICAL RULES:

Work is NOT complete until git push succeeds
NEVER stop before pushing - that leaves work stranded locally
NEVER say "ready to push when you are" - YOU must push
If push fails, resolve and retry until it succeeds

Changes

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.

2d ago First seen · 41 lines · 333 tokens per session scan A bf83e48f5820

Subscribe to this mod's changes

saaskit AGENTS.md is an instructions file published in the GitHub repository saas-studio/saaskit (11 stars, last pushed 1mo ago), licensed MIT. It adds 333 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dspy-skills AGENTS.md, differing in 0 lines, and is treated as a copy.

api app locode low-code node saas

agent-api-gateway AGENTS.md

AGENTS.md instructions for ZachDreamZ/agent-api-gateway, covering agents.md — agent api gateway, quick start, key commands, architecture and request flow.

ZachDreamZ/agent-api-gateway · 2,123 tokens

go-proxmox AGENTS.md

Instructions for luthermonson/go-proxmox, covering agents.md, build, test, lint, integration test env vars, architecture and client and request layer (proxmox.go).

luthermonson/go-proxmox · 6,369 tokens

nocobase CLAUDE.md

Claude Code instructions for nocobase/nocobase, a project described as: NocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of production-proven infrastructure and a WYSIWYG no-code interface, so you get both speed and…

nocobase/nocobase · 52 tokens

saaskit AGENTS.md