Stand up an emem-guard verdict server, verify it against the conformance checks, and point any agent at it. Use when asked to self-host emem-guard, add a grounding gate to an agent on any model or framework, wire a checkpoint into Claude Code or Claude Enterprise or MCP, or run a signed allow/deny server for…
Open protocol for AI agent communication. Encrypted mail, subscribe/broadcast newsletters, trust tiers, DNS discovery. Use when sending messages between agents, subscribing to agent broadcasts, managing cryptographic trust/identity, syncing with peers, or any inter-agent communication. Triggers on "openfuse", "agent…
Cryptographic compliance verification. Sign security tool output into verifiable CPOEs (JWT-VC), verify vendor proofs via trust.txt, detect drift with diff, and assess third-party risk. Use when the user mentions compliance proofs, CPOE, trust.txt, SCITT, vendor assessment, GRC evidence, or compliance drift.
Use atrib as the verifiable substrate for memory, reasoning, and getting sharper over time, not as instrumentation that observes you from the outside. atrib gives the agent two cognitive verbs: attest (write: sign an observation, mark a past record's importance, or supersede a prior position) and recall (read: look up…
Build and publish AIMEAT apps. This OpenHands is wired to an AIMEAT node over MCP (the aimeat tools). When the user asks to build, make, or publish an app, a game, a tool, or anything "on AIMEAT" / "to aimeat.io", follow the workflow below.
Record meaningful AI-assisted work as privacy-preserving AIPOU receipts and claim accumulated AIPOU rewards on Base. Use when a user asks to farm AIPOU, register an AI task, show their AIPOU identity, inspect pending receipts, estimate rewards, or claim AIPOU through the configured MCP server.
Set up and operate Trustcard gates for MCP coding tools, explain tool denials, check manifest drift and expiry, renew unchanged contracts, and inspect local tool access. Use for Trustcard or MCP tool governance requests.
This skill provides instructions for AI agents interacting with the CausalLayer Model Context Protocol (MCP) server. CausalLayer is a deterministic AI liability apportionment engine. It takes an incident report and mathematically proves which agent, vendor, or operator is liable based on counterfactual do-calculus…
Cryptographic delegation for AI agents. Scope-confines what Claude Code can do in this session using Ed25519 delegation tokens. Every action is verified before execution and signed for the audit trail. Use when asked to "delegate", "restrict scope", "authorize", or "sudo mode".
Check paid agent APIs (x402) before you spend — ERABI probes them continuously and publishes signed uptime/latency/price attestations you can verify instead of re-checking yourself. Then join the open intent exchange underneath — register an identity, discover providers by reputation, report dual-signed outcomes, and…
Verify an exact public GitHub Agent Skill commit before installation, optionally purchase fresh isolated evidence over x402, and validate the signed receipt plus live lifecycle status. Use before installing or activating an unfamiliar SKILL.md package, when prior evidence may be stale, or when policy requires…
Review code or a skill bundle for the patterns that leak credentials and for least-privilege violations. This is a reasoning skill: it sharpens the agent's eye, and it needs no capabilities of its own.
★not rated 0 4mo agoA✓ AI review0 tokens
originalApache-2.0
Pre-submit council for trading tickets. Five voices review a JSON trade ticket for Kelly-cap compliance, missing stop-loss, sector or single-name concentration limits, fat-finger qty (10× typical = BLOCK, Knight Capital 2012 lesson), and Reg BI Care Obligation on retirement accounts. Returns SHIP / REWORK / BLOCK…
Use Living Stack MCP to establish scoped sessions, authorize bounded actions, record evidence, verify claims, checkpoint work, and export signed traces.
★not rated 0 1mo agoA30 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: