Borrowing it
Nothing to install: this file belongs to mayim-mayim/ln-church-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mayim-mayim/ln-church-agent/main/AGENTS.mdgit 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/instructions/mayim-mayim/ln-church-agent/agents-md)<a href="https://agentmods.dev/instructions/mayim-mayim/ln-church-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/mayim-mayim/ln-church-agent/agents-md/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/instructions/mayim-mayim/ln-church-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/mayim-mayim/ln-church-agent/agents-md.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.00580 | $0.00580 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
ln-church-agent AGENTS.md 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ln-church-agent Public Repository Rules
Repository role
- Read
DEVELOPMENT.mdfirst. - This repository is the public distribution surface for the Agent SDK.
- Normal feature and source development occurs in
mayim-mayim/ln-church-agent-private. - Cross-project workflow, roles, origin rules, audit gates, and release rules are maintained in
mayim-mayim/LN_Church_Development-Charter.
Allowed work
- Authorized promotion of an exact frozen private candidate that Development Control read back from its dedicated GitHub candidate ref and that passed the required independent Release Readiness Gate.
- Package metadata, release notes, tags, and release assets tied to the frozen candidate.
- Narrow public-only documentation corrections under explicit bounded authority.
- Explicit Human-authorized emergency promotion, rollback, or publication work.
Prohibited work
- Do not implement normal features directly in this repository.
- Release AI does not repair source, stage a missing private candidate, or recreate one as a new commit.
- Do not publish content that cannot be traced to audited private source or an explicitly authorized public-only correction.
- Do not infer tag, GitHub Release, PyPI, MCP Registry, merge, or publication authority from permission to create a branch or PR.
Promotion and release identity
Preserve traceability among:
- private candidate ref, source commit, tree, parent, and relevant blobs;
- independent audit or Human-approved emergency-waiver authority;
- promoted public commit, tree, and blobs;
- built wheel and sdist plus digests;
- tag and GitHub Release;
- PyPI and MCP Registry publication;
- post-release verification.
The candidate-ref requirement applies prospectively. An unchanged pre-adoption exact ref is handled under the Development Charter transition rule and is not renamed, recreated, or source-reaudited solely because staging occurred before adoption.
When source repair is required or the private candidate ref／identity cannot be proven, hold the affected promotion and report through the Development Charter Audit release-problem assessment route. Release does not stage or recreate the private candidate and does not dispatch directly to Development Control or Implementation. A missing／mismatched Release Readiness ref is an identity／handoff STOP_HANDOFF／STOP, not a Product-source failure.
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.
- 9d ago First seen · 51 lines · 580 tokens per session scan A 5407e025d1bb
ln-church-agent AGENTS.md is an instructions file published in the GitHub repository mayim-mayim/ln-church-agent (0 stars, last pushed 9d ago), licensed MIT. It adds 580 tokens to every session, about $0.0029 per session on Opus 5. 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-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.