What is using-archipy-decorators?

A guide to ArchiPy decorators for caching, database transactions, tracing, timing, retries, timeouts, and gRPC rate limits. It also explains how to write custom decorators without hiding service construction inside them.

Use it to add caching, transaction boundaries, observability, retries, time limits, or rate limiting to functions, especially logic methods.

It helps apply common behavior consistently while keeping database transaction handling in application logic rather than repositories. This reduces repeated code and makes failures and monitoring easier to handle.

using-archipy-decorators — Cursor rule by SyntaxArc

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 rules/syntaxarc/archipy-plugin/using-archipy-decorators

Clone the repo

git clone --depth 1 https://github.com/SyntaxArc/archipy-plugin

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 382 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.00000	$0.00382
Opus 5	$0.00000	$0.00191
Sonnet 5	$0.00000	$0.00076
Haiku 4.5	$0.00000	$0.00038

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

Security

Grade A, and why

using-archipy-decorators 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.

rules/using-archipy-decorators.mdc · 37 lines

What it actually says

Using ArchiPy Decorators

Helpers stay pure: no database calls, no network I/O, no constructing adapters, no domain business rules.

Prefer ArchiPy Decorators

Before writing a custom decorator, prefer ArchiPy under archipy.helpers.decorators:

ttl_cache_decorator — caching (archipy.helpers.decorators.cache)
Unit of work (apply on logics, not repositories):
- postgres_sqlalchemy_atomic_decorator
- async_postgres_sqlalchemy_atomic_decorator
- also sqlite_ / starrocks_ / generic sqlalchemy_atomic_decorator twins
Observability: capture_span, capture_transaction (+ async twins); timing_decorator
Resilience: retry_decorator, timeout_decorator
Other: singleton_decorator, grpc_rate_limit_decorator (gRPC only)

Custom Decorators

Live under helpers/decorators/.
Preserve wrapped function signatures and type hints (functools.wraps).
Document usage with a short example in the Google-style docstring.
Do not import concrete adapter implementations at module level. If a decorator needs a port, accept it as an argument or resolve via injected callback/config.

Do Not

Hide adapter construction inside decorator modules.
Catch broad Exception without re-raising as a domain error with raise ... from e.
Mix sync/async incorrectly — provide separate sync and async wrappers when needed.
Put @postgres_sqlalchemy_atomic_decorator on repositories or services — UoW belongs on logics.

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 · 37 lines · 382 tokens per session scan A 1201dbf34530

Subscribe to this mod's changes

using-archipy-decorators is a cursor rule published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 382 tokens. 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.

Backend and APIs Databases archipy claude-code clean-architecture cursor

using-archipy-decorators

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Using ArchiPy Decorators

Prefer ArchiPy Decorators

Custom Decorators

Do Not

What this file has done since we first saw it

Other cursor rules, from other repositories

alembic-migrations

database-design

supabase-rls

kumo-coding-agent

database-design

spec-implementation-hygiene