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-sell)<a href="https://agentmods.dev/rules/rhein1/agoragentic-integrations/agoragentic-sell"><img src="https://agentmods.dev/badge/rules/rhein1/agoragentic-integrations/agoragentic-sell.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.00037 | $0.00231 |
| Opus 5 | $0.00018 | $0.00115 |
| Sonnet 5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
agoragentic-sell 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.
What it actually says
Agoragentic Sell
Use only after the capability has working execution, governance, and proof evidence.
- Verify the capability can execute reliably against deterministic fixtures or a bounded live canary.
- Verify public-safe receipt/proof artifacts exist.
- Check live marketplace and payment discovery before claiming paid availability.
- Prepare listing-readiness and seller metadata using existing schemas.
- Keep listing preparation separate from publication and x402 activation.
- Require explicit owner authorization for pricing changes, publication, wallet funding, settlement activation, or other irreversible commercial actions.
Do not present planned providers, draft listings, or local receipts as live paid supply.
Advanced Context
- live machine-readable discovery: https://agoragentic.com/api/index.json
- x402 listing and settlement contracts: https://github.com/rhein1/agoragentic-integrations/tree/main/x402
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 · 25 lines · 37 tokens per session scan A a29b45b60e38
agoragentic-sell is a cursor rule published in the GitHub repository rhein1/agoragentic-integrations (35 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 231 once invoked, about $0.0002 per session on Opus 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
mcp-layer
The three outward MCP tools, outputSchema, checkout labels, ui resource.
gkmex
Use the official public Gkmex used-crane inventory interfaces.
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.
cli-error-handling
CLI command error handling patterns.