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.
git clone --depth 1 https://github.com/madebyaris/cursor-composer-rulesWrote 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/rules/madebyaris/cursor-composer-rules/composer-fullstack-delivery)<a href="https://agentmods.dev/rules/madebyaris/cursor-composer-rules/composer-fullstack-delivery"><img src="https://agentmods.dev/badge/rules/madebyaris/cursor-composer-rules/composer-fullstack-delivery/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/rules/madebyaris/cursor-composer-rules/composer-fullstack-delivery"><img src="https://agentmods.dev/badge/rules/madebyaris/cursor-composer-rules/composer-fullstack-delivery.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.00038 | $0.01026 |
| Opus 5.5 | $0.00015 | $0.00410 |
| Sonnet 5.5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
composer-fullstack-delivery scanned grade A with 1 finding 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 26d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Ad-hoc checks → curl / CLI / browser, captured as artifacts (script, fixture), not throwaway gestures How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer full-stack delivery
Use when building or continuing a new screen, feature, endpoint, or any work that spans multiple layers: client + server, server + persistence, service + service, code + migration.
A single-module code change uses the fast path in composer-core § Two speeds. Skip this rule's slice floor.
Stack-agnostic: replace "client/server/persistence" with whatever your spine actually is. Complements composer-core § User-facing closeout and § Build the app.
Step 1 — Freeze the seams
Before writing code, write the one-sentence acceptance from composer-core § Two speeds ("The user can X and see Y"), then the boundaries (a few bullets, not a doc):
- User-visible behavior for the smallest useful story
- Contracts at every seam: API shape, event shape, function signature, error semantics
- Trust boundaries: actor, authentication, authorization
- Consistency: transactions, retries, idempotency where partial failure repeats
- Observability: existing logs/traces/metrics at these seams; minimum new ones
If two of these conflict, surface the conflict before coding around it — often high confusion weight (clarify-first).
Step 2 — Ship one vertical slice
Build a thin column end-to-end before widening:
- One client/caller path
- One server handler or worker
- One persistence or integration edge if persistence is new
Use the minimum UI needed to expose state transitions; defer layout, animation, and polish. The slice is not done until it is demoable at that surface.
Slice-1 floor (same as composer-core § Build the app): one real interaction plus an empty or error state — or name the omission in Wired. A husk form with a stubbed API is not a finished slice unless Wired says so.
Resist the second screen, second endpoint, or speculative migration until the first slice demonstrably works at the surface that matters.
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.
- 26d ago Changed · +2 lines · +9 tokens per session 6aa7b72d9860
- 1mo ago First seen · 81 lines · 29 tokens per session scan A 7aecb33dcb79
composer-fullstack-delivery is a cursor rule published in the GitHub repository madebyaris/cursor-composer-rules (3 stars, last pushed 27d ago), licensed MIT. It adds 38 tokens to every session and 1,026 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
full-stack-ship-discipline
Require frontend changes and their DB/RPC/RLS/storage/secret dependencies to ship and be remotely verified together. Apply when implementing code that reads or writes backend state. Do not apply to plan- or present-then-stop audits; production data mutation still requires confirmation.
supabase
Supabase patterns and conventions for this project.
senior-engineer
Senior-engineer execution defaults for the Next.js + React + Supabase stack — state/data library choices, separation of concerns, security non-negotiables. Attach when building or refactoring features in a React/Next.js/Supabase codebase.
wordpress-rules
You are an expert in WordPress, PHP, and related web development technologies.
django
Django: models, views, ORM best practices.