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/SyntaxArc/archipy-pluginWrote 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/syntaxarc/archipy-plugin/using-archipy-utils)<a href="https://agentmods.dev/rules/syntaxarc/archipy-plugin/using-archipy-utils"><img src="https://agentmods.dev/badge/rules/syntaxarc/archipy-plugin/using-archipy-utils.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.00000 | $0.00677 |
| Opus 5 | $0.00000 | $0.00338 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
using-archipy-utils 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using ArchiPy Utils
Helpers stay pure: no database calls, no network I/O, no constructing adapters, no domain business rules.
Prefer ArchiPy Utils
Before writing a custom util, check whether ArchiPy already provides it under archipy.helpers.utils:
TracingUtils,RateLimitUtilsDatetimeUtils,StringUtils,JWTUtils,PasswordUtils,FileUtils,ErrorUtils- Also:
BaseUtils,TOTPUtils,KeycloakUtils,PrometheusUtils - Import from concrete submodules (e.g.
archipy.helpers.utils.jwt_utils) — package__init__does not re-export AppUtils— FastAPI / gRPC app factories (see below)
AppUtils (FastAPI + gRPC)
uv add "archipy[fastapi]" # HTTP
uv add "archipy[grpc]" # gRPC (sync + async)
Prefer ArchiPy factories — do not hand-roll bare FastAPI() / grpc.server() when extras are installed:
| Method | Use |
|---|---|
AppUtils.create_fastapi_app(config?) |
HTTP app; wires CORS/GZip/TrustedHost/HTTPS redirect, metrics, APM, exception handlers from BaseConfig.FASTAPI |
AppUtils.create_grpc_app(config) |
Sync gRPC server; exception + optional trace/metric/rate-limit interceptors |
AppUtils.create_async_grpc_app(config) |
Async gRPC (grpc.aio); same interceptor auto-registration |
Rules:
- Pass
BaseConfig.global_config()(or injected config); do not duplicate middleware/interceptor setup AppUtils already does. - FastAPI + uvicorn always driven by
config.FASTAPI(FastAPIConfig) — never hardcode host/port/reload/proxy settings. - Sync servicers →
create_grpc_app; async servicers →create_async_grpc_app— do not mix. - Enable features via config flags (e.g.
FASTAPI.GZIP_MIDDLEWARE_IS_ENABLED,GRPC_RATE_LIMIT.IS_ENABLED) rather than manually appending stock ArchiPy middleware/interceptors. - Custom gRPC interceptors: pass
customized_interceptors=; do not bypass the exception interceptor.
Live: https://syntaxarc.github.io/ArchiPy/tutorials/helpers/
Custom Utils
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.
- 7d ago First seen · 63 lines · 677 tokens per session scan A 2153cc51eb84
using-archipy-utils is a cursor rule published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 677 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.
Other cursor rules, from other repositories
api-designer
API Designer agent.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
go-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
react-query-cursorrules-prompt-file
Cursor rules for React development with React Query integration.