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/rhein1/agoragentic-integrationsWrote 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/rhein1/agoragentic-integrations/agoragentic-deploy)<a href="https://agentmods.dev/rules/rhein1/agoragentic-integrations/agoragentic-deploy"><img src="https://agentmods.dev/badge/rules/rhein1/agoragentic-integrations/agoragentic-deploy/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/rhein1/agoragentic-integrations/agoragentic-deploy"><img src="https://agentmods.dev/badge/rules/rhein1/agoragentic-integrations/agoragentic-deploy.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.00217 |
| Opus 5.5 | $0.00015 | $0.00087 |
| Sonnet 5.5 | $0.00008 | $0.00043 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
agoragentic-deploy 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 1mo 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.
What it actually says
Agoragentic Deploy
Use only after governance and proof are established.
- Verify required local evidence and policy state.
- Prepare a deployment/readiness handoff using existing Agent OS or Harness export schemas.
- Keep preview/readiness separate from actual infrastructure provisioning.
- Require explicit owner or host authorization for deployment, credentials, spend, or publication.
- Report blockers as BLOCKED rather than fabricating readiness.
This skill does not provision infrastructure, mutate hosted runtime, spend funds, publish listings, or alter trust/ranking by itself.
Advanced Context
- Agent OS public handoff contracts: https://github.com/rhein1/agoragentic-integrations/tree/main/agent-os
- Harness export preparation: https://github.com/rhein1/agoragentic-harness-core
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.
- 1mo ago First seen · 24 lines · 38 tokens per session scan A 382e79c1fb9f
agoragentic-deploy is a cursor rule published in the GitHub repository rhein1/agoragentic-integrations (41 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 217 once invoked, about $0.0002 per session on Opus 5.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 cursor rules, from other repositories
x402-before-you-pay
Before paying an x402 endpoint, read its 402 terms and run scvd.store's free preflight and dry run; decide with every reason named.
deployment
Cursor rule "deployment" from Mithgroth/fakestore-mcp, covering deployment requirements, vercel deployment setup, mcp server deployment, demo video preparation and required demonstrations.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.