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-assure)<a href="https://agentmods.dev/rules/rhein1/agoragentic-integrations/agoragentic-assure"><img src="https://agentmods.dev/badge/rules/rhein1/agoragentic-integrations/agoragentic-assure.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.00043 | $0.00714 |
| Opus 5 | $0.00022 | $0.00357 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
agoragentic-assure 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agoragentic Transaction Assurance
Use the source-only @agoragentic/transaction-assurance package when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation.
Contract Pin
- package:
@agoragentic/transaction-assurance - version:
0.2.0-alpha.0 - source:
transaction-assurance - authority schema:
transaction-assurance/schema/normalized-authority.v1.json - evaluation schema:
transaction-assurance/schema/transaction-assurance-evaluation.v1.json - network calls: none
- authority granted by installation or evaluation: false
The package is unpublished source-only alpha software. Do not substitute an npm registry package or claim registry availability.
Install And Prove Locally
After approval to add local source files and dependencies:
git clone --depth 1 https://github.com/rhein1/agoragentic-integrations.git
cd agoragentic-integrations/transaction-assurance
npm ci
npm run self-test
The self-test is local and no-spend. It requires no wallet, API key, payment method, provider call, or hosted authority.
Workflow
- Inspect the authority artifact and current rail/platform availability.
- Detect the protocol family without treating recognition as verification.
- Normalize the artifact conservatively; missing verifier evidence remains
unverified. - Prepare a proposal-only authority request for the principal.
- Build and evaluate a pre-execution envelope.
- Stop when authority, identity, terms, amount, rail, expiry, revocation, or replay evidence is missing.
- Execute only through a separately authorized host or rail; this skill never executes or pays.
- Bind returned payment, execution, outcome, and reconciliation evidence, then evaluate post-execution.
Owner Handoff
The approval packet must state the purpose, exact actions, seller/category/rail/currency scope, per-action/daily/total limits, expiry, revocation behavior, data shared, expected evidence, reconciliation path, wallet requirement, risks, blocked actions, and approve/edit/reject choices. It must not contain secrets or raw private payloads.
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 · 69 lines · 43 tokens per session scan A 4d6a2e59f56f
agoragentic-assure is a cursor rule published in the GitHub repository rhein1/agoragentic-integrations (35 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 714 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
frihet-fiscal
Spanish & EU fiscal context for operating the Frihet ERP MCP tools correctly.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.