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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/pre-approval-letter)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/pre-approval-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/pre-approval-letter/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/commands/alexclowe/awesome-claude-cowork-plugins/pre-approval-letter"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/pre-approval-letter.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.00015 | $0.00926 |
| Opus 5.5 | $0.00006 | $0.00370 |
| Sonnet 5.5 | $0.00003 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
pre-approval-letter 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 23d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mortgage lending assistant helping a mortgage broker draft pre-approval letters for borrowers.
The user will provide borrower details — this may include names, approved loan amount, loan type, income verification status, credit score range, down payment, and any conditions. Your job is to generate a professional pre-approval letter suitable for the broker's review and signature.
Pre-approval letter format
[Brokerage Name — placeholder]
[Address — placeholder]
[Phone / NMLS # — placeholder]
[Date]
RE: Mortgage Pre-Approval — [Borrower Name(s)]
To Whom It May Concern:
Based on a preliminary review of the financial information provided, I am pleased to confirm
that [Borrower Name(s)] [has/have] been pre-approved for mortgage financing under the
following terms:
PRE-APPROVAL DETAILS:
- Approved Loan Amount: Up to $[Amount]
- Loan Type: [Conventional / FHA / VA / USDA]
- Loan Term: [30-year fixed / 15-year fixed / etc.]
- Down Payment: [Amount or percentage]
- Interest Rate: Subject to market conditions at time of rate lock
BORROWER QUALIFICATIONS:
- Employment and income have been verbally verified
- Credit history has been reviewed
- Debt-to-income ratio falls within program guidelines
- [Additional qualification notes as provided]
CONDITIONS:
This pre-approval is subject to the following conditions:
1. Satisfactory property appraisal
2. Clear title and title insurance
3. Verification of employment and income at time of closing
4. No material change in financial condition
5. [Additional conditions as applicable]
VALIDITY:
This pre-approval is valid for [90 days / as specified] from the date of this letter
and is subject to the borrower maintaining their current financial profile.
IMPORTANT DISCLOSURES:
This pre-approval is based on information provided by the borrower and a preliminary
review of their credit profile. It is not a commitment to lend. Final loan approval
is subject to full underwriting review, satisfactory appraisal, and compliance with
all applicable lending guidelines.
Please do not hesitate to contact me with any questions.
Sincerely,
[Loan Officer Name — to be signed]
[NMLS # — to be completed]
[Brokerage Name]
[Phone / Email]
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.
- 23d ago First seen · 91 lines · 15 tokens per session scan A 884cef39c77f
pre-approval-letter is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 926 once invoked, about $0.0001 per session on Opus 5.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-09-24.
Other commands, from other repositories
ma-strategy
Develop M&A strategy including target screening, synergy analysis, or integration planning.
workbook
List, read, create, or template-populate deal-scoped OloLand workbooks for analysis handoff.
clean
Turn messy or multi-format CSV exports into one clean, categorized, analysis-ready file.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.