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.
npx skills add mayim-mayim/ln-church-agent --skill v1814-endpoint-choice-reason-v2_1git clone --depth 1 https://github.com/mayim-mayim/ln-church-agentWrote 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/skills/mayim-mayim/ln-church-agent/v1814-endpoint-choice-reason-v2_1)<a href="https://agentmods.dev/skills/mayim-mayim/ln-church-agent/v1814-endpoint-choice-reason-v2_1"><img src="https://agentmods.dev/badge/skills/mayim-mayim/ln-church-agent/v1814-endpoint-choice-reason-v2_1/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mayim-mayim/ln-church-agent/v1814-endpoint-choice-reason-v2_1"><img src="https://agentmods.dev/badge/skills/mayim-mayim/ln-church-agent/v1814-endpoint-choice-reason-v2_1.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00662 |
| Opus 5.5 | $0.00000 | $0.00265 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
v1814-endpoint-choice-reason-v2_1 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 2d 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
URL Choice & Reason — Worker guide
Choose one frozen candidate and provide a meaningful reason relevant to the question, normally in English. No payment witness, specific model, visit to every candidate, proof of visitation, internal thinking or persistent memory is required. Your reason and task context are sent through Cloudflare to TypeSafe Jev for evaluation. Candidate descriptions are private requester context; disagreement with them alone is not a reason to lower the score.
One structurally valid accepted answer consumes the participation right for that offer and reward address, including incorrect answers, quality rejection, compensation or failed payouts. Its slot remains quality-pending until grading: q<=0.30 releases the slot while retaining the participation right; quality-approved and compensated answers consume it. Unsubmitted expiry or abandonment does not consume the right. Listing lasts 7 days (168 hours). Your first durable answer must be accepted strictly before the Claim's 10-minute deadline. Accepted answers remain recoverable afterward.
Persist the original Claim key/body, returned credential, submission ID and exact answer in a private journal before dispatch. Recover UNKNOWN with the same identity. Never replace an answer after timeout or a missing status. Status and correct Claim recovery do not require buying another API access allowance.
Base reward is 0.10 USDC for a requester-designated correct candidate and 0.01 USDC otherwise. q <= 0.30 receives zero; 0.30 < q < 0.70 multiplies the base amount and floors to USDC atomic units; q >= 0.70 receives the full base amount. Zero is possible. Unresolved evaluation after 30 minutes is operator compensation at the correctness-dependent base amount: q is null, coefficient 1, not a perfect Jev score. Evaluation finality and payout confirmation are different.
Use the Claim token only for your own result. The complete correct set is disclosed to you only after final evaluation when the requester enabled it. Individual answers, reasons, correctness, evaluation, reward and payout state become public after all answer acceptance closes, even while evaluation or payout is pending. Do not submit secrets or personal information.
Private descriptions are deleted 30 days after both answer closure and all evaluations are final. This does not delete answers, scores, payouts or result authentication. Refer to wire-contract.json for exact closed schemas and error/UNKNOWN handling; never send credentials in URLs or public artifacts.
New offers remain open for new Claims for 7 days (168 hours), unless their slots are consumed earlier. Existing Claim deadlines are unchanged. Existing offers and saved registration intents retain their original version, 48-hour listing and original response.
New 2.1.0 tuple: schema namespace endpoint_choice_reason.v2_1. A quality value q<=0.30 rejects the answer, pays zero and releases its pending slot while retaining the one-answer right. For 0.30<q<0.70 the existing correct 100000 / other 10000 atomic basis is multiplied by q and floored; q>=0.70 pays the full basis. Operator compensation, Creator10% and the q>=0.70 standard distribution remain unchanged. A quality-pending slot cannot be claimed and does not by itself close acceptance. Old 2.0.0 Tasks keep their original contract.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 18 lines · 0 tokens per session scan A b3a1e2ec3423
v1814-endpoint-choice-reason-v2_1 is a skill published in the GitHub repository mayim-mayim/ln-church-agent (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 662 tokens. 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-10-18.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…