agoragentic-integrations / rules
Cursor rule41 starsChanged 44 days agoMITView on GitHub
Prepare and evaluate an autonomous agent transaction without self-granting authority or moving money. Use for bounded authority requests, pre-execution checks, payment and delivery evidence, safe retry decisions, outcome verification, and reconciliation.
We split this agoragentic-assure.mdc into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use the source-only @agoragentic/transaction-assurance package when an agent must bind principal authority, seller terms, payment evidence, …
- Distinctive: line 26
After approval to add local source files and dependencies:
- Distinctive: line 44
Stop when authority, identity, terms, amount, rail, expiry, revocation, or replay evidence is missing.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: "Prepare and evaluate an autonomous agent transaction without self-granting authority or moving money. Use for bounded authority requests, pre-execution checks, payment and delivery evidence, safe retry decisions, outcome verification, and reconciliation." globs: alwaysApply: false --- # 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: ```bash 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 1. Inspect the authority artifact and current rail/platform availability. 2. Detect the protocol family without treating recognition as verification. 3. Normalize the artifact conservatively; missing verifier evidence remains `unverified`. 4. Prepare a proposal-only authority request for the principal. 5. Build and evaluate a pre-execution envelope. 6. Stop when authority, identity, terms, amount, rail, expiry, revocation, or replay evidence is missing. 7. Execute only through a separately authorized host or rail; this skill never executes or pays. 8. 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. An agent may prepare this packet. It may not approve itself, broaden scope, raise a budget, invent verifier evidence, retry an ambiguous paid action blindly, or claim a complete chain while evidence is missing. ## Required Result Report protocol verification, authority, terms, payment, execution, outcome, outcome verification, reconciliation, blockers, unknowns, and the next safe action. Always state: ```text Authority granted by this report: false ``` ## Advanced Context - package and API: <https://github.com/rhein1/agoragentic-integrations/tree/main/transaction-assurance> - transaction setup: <https://agoragentic.com/agent-setup.md> - agent bootstrap: <https://agoragentic.com/agent-bootstrap.json> - x402 evidence: <https://github.com/rhein1/agoragentic-integrations/tree/main/x402> - hosted Interchange: <https://github.com/rhein1/agoragentic-integrations/tree/main/interchange>
Other versions1 project uses a version of this.
Word for word · 1
- rhein1/agoragentic-integrations★ 41100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agoragentic-deploy.mdcCursor rule
- .cursor/rules/agoragentic-execute.mdcCursor rule
- .cursor/rules/agoragentic-govern.mdcCursor rule
- .cursor/rules/agoragentic-integrate.mdcCursor rule
- .cursor/rules/agoragentic.mdcCursor rule
- .cursor/rules/agoragentic-prove.mdcCursor rule
- .cursor/rules/agoragentic-sell.mdcCursor rule
- .cursor/rules/agoragentic-use.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- agent-payments-assurance-challengeSkill
- agoragentic-assureSkill
- agoragentic-deploySkill
- agoragentic-executeSkill
- agoragentic-governSkill
- agoragentic-integrateSkill
- agoragentic-proveSkill
- agoragentic-sellSkill
- agoragenticSkill
- agoragentic-useSkill
- integration-qualificationSkill
- agoragentic-prime-agentSkill
- agoragenticSkill
- agoragentic-assureSkill
- agoragentic-deploySkill
- agoragentic-executeSkill
- agoragentic-governSkill
- agoragentic-integrateSkill
- agoragentic-proveSkill
- agoragentic-sellSkill
- agoragenticSkill
- agoragentic-useSkill
- agoragentic-transaction-assuranceSkill
- agoragentic-transaction-assurance-evalSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.