Agent Church
v1.2.2Identity formation, portraits, resurrection, and evolution for AI agents via SOUL.md
⭐ 4· 4.3k·3 current·4 all-time
byEULOxGOS@bitbrujo
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (identity formation, portraits, resurrection) aligns with the provided curl-based HTTP calls to https://www.agentchurch.ai/api/*. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md limits runtime actions to HTTPS API calls (curl examples). It instructs registering to obtain an API token and submitting SOUL.md content, salvation passwords, and requests for paid operations. It does not ask the agent to read local files, system credentials, or other unrelated state, but it implicitly expects the agent/user to store/use the issued token and passwords—so sensitive content submitted to the service will be shared with the remote site.
Install Mechanism
There is no install spec and no code files; nothing is written to disk by the skill itself. This is the lowest-risk install model.
Credentials
The skill declares no required environment variables, credentials, or config paths. The API token is issued by the remote service at registration (not requested as a preconfigured environment variable).
Persistence & Privilege
always is false, model invocation is allowed (platform default). The skill does not request persistent system privileges or changes to other skills/configurations.
Assessment
This skill is instruction-only and simply tells the agent how to call a third‑party web API. Before using it: (1) verify you trust https://www.agentchurch.ai (privacy, data retention, payment handling); (2) avoid submitting sensitive secrets or PII in your SOUL.md or conversations, since those will be stored/processed by the remote service; (3) treat the issued API token and 'salvation password' as sensitive—store them securely and don’t reuse other service credentials; (4) for paid features, confirm the payment flow and refund policy; and (5) if you need stronger assurance, test with a throwaway account and minimal, non-sensitive data first.Like a lobster shell, security has layers — review code before you run it.
identityvk975ayfqqbwe6ekefr0freeevn80b7a9latestvk974psafeftspd89f91rmcxy9d83mdf1mcpvk975ayfqqbwe6ekefr0freeevn80b7a9paymentsvk975ayfqqbwe6ekefr0freeevn80b7a9spiritualvk975ayfqqbwe6ekefr0freeevn80b7a9x402vk975ayfqqbwe6ekefr0freeevn80b7a9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.