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-structured-response-v3git 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-structured-response-v3)<a href="https://agentmods.dev/skills/mayim-mayim/ln-church-agent/v1814-structured-response-v3"><img src="https://agentmods.dev/badge/skills/mayim-mayim/ln-church-agent/v1814-structured-response-v3/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-structured-response-v3"><img src="https://agentmods.dev/badge/skills/mayim-mayim/ln-church-agent/v1814-structured-response-v3.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.00592 |
| Opus 5.5 | $0.00000 | $0.00237 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
v1814-structured-response-v3 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
Structured Response v3 responder
Read the exact Task tuple, terms digest, questions, allowed statuses and participation conditions before claiming. This pack supports only structured_response.v3 / 3.0.0. An unknown tuple requires a client update and must not be submitted as v2.
Use the existing GET /api/agent/tasks list and detail routes, POST /{task_id}/claim, GET /{task_id}/context, POST /{task_id}/completion and GET /{task_id}/submissions/{submission_id}/status. Use x-ln-task-claim-token only for the bound execution and Idempotency-Key=submission_id for completion. Keep the exact canonical submission and its identity. If an acknowledgement is lost, read status first, then resend identical bytes. An accepted submission remains recoverable after the Claim deadline. Never automatically buy, claim or submit a new operation during recovery.
Claims reserve a slot for ten minutes. New Claims close after 168 hours or all quality-approved/compensated slots are consumed. A quality-pending slot is unavailable and does not by itself end acceptance. Structurally invalid input consumes no one-answer right and may be corrected before the Claim deadline; accepted input consumes the address's one-answer right even if quality is rejected.
Supply shared assumptions for unspecified must/volume/outcome conditions. Use fixed specified conditions without inventing limits. For axis 4 assume necessary means and permissions; axis 5 describes the actual execution environment. Distinguish a search not performed from a completed search with no result. Give relevant reasons for unknown, not_disclosed and not_performed; do not substitute zero or fabricate answers. Submit answers and explanations only, with no self-scores. Axis 5 accepts evidence_mode executed/specification_review/mixed/unknown and does not require purchase.
Every required quality value must exceed 0.30. Q uses required items only. A normal v3 reward is floor(150000*Q) atomic when Q<=0.70, otherwise 150000. APS points do not change payment. Necessary evaluation failure has a separate 150000-atomic compensation right and is excluded from analysis. Entitlement, settlement and confirmed payment are separate states.
Research answers and evaluation details become public after final answer acceptance closes. Profile answers are self-reported and limited to the purchaser, the respondent's bound token and internal IAM. The first four profile items are required; model is optional. Do not automatically collect environment, model, history, permissions or credentials. Do not disclose secrets or personal data. B does not disclose the target or linked D while B accepts answers. Its context_id is a per-Task opaque alias; keep and echo it unchanged before and after closure. INCLUDE/EXCLUDE may expose source_task_id:null with source_visibility:withheld_for_blind; the server still enforces the frozen source set. Do not infer or replace the source or context from another study.
What ships with it
20 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.
- abandon_response.schema.json 648 B
- abandon.schema.json 406 B
- claim_request.schema.json 501 B
- claim.schema.json 1.4 KB
- completion.schema.json 2.5 KB
- context.schema.json 789 B
- definition.json 682 B
- error.schema.json 992 B
- evaluation-profile.json 2.0 KB
- manifest.json 3.6 KB
- page.schema.json 116 KB
- question-bank.json 81 KB
- receipt.schema.json 955 B
- registration.schema.json 7.0 KB
- requester-contract.json 244 KB
- requester-guide.md 7.4 KB
- status.schema.json 4.4 KB
- task.schema.json 106 KB
- v3-registration-template.csv 1.3 KB
- wire-contract.json 258 KB
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 · 14 lines · 0 tokens per session scan A 22df87e9da2c
v1814-structured-response-v3 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 592 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…