Borrowing it
Nothing to install: this file belongs to alirezaebrahimi5/ai-senior-engineer-template. 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/alirezaebrahimi5/ai-senior-engineer-template/main/.claude/skills/llm-app-patterns/SKILL.mdgit clone --depth 1 https://github.com/alirezaebrahimi5/ai-senior-engineer-templateWrote 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/alirezaebrahimi5/ai-senior-engineer-template/llm-app-patterns)<a href="https://agentmods.dev/skills/alirezaebrahimi5/ai-senior-engineer-template/llm-app-patterns"><img src="https://agentmods.dev/badge/skills/alirezaebrahimi5/ai-senior-engineer-template/llm-app-patterns/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/alirezaebrahimi5/ai-senior-engineer-template/llm-app-patterns"><img src="https://agentmods.dev/badge/skills/alirezaebrahimi5/ai-senior-engineer-template/llm-app-patterns.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.00054 | $0.04942 |
| Opus 5 | $0.00027 | $0.02471 |
| Sonnet 5 | $0.00011 | $0.00988 |
| Haiku 4.5 | $0.00005 | $0.00494 |
Grade A, and why
llm-app-patterns 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago First seen · 761 lines · 54 tokens per session scan A 6ba59c050663
llm-app-patterns is a skill published in the GitHub repository alirezaebrahimi5/ai-senior-engineer-template (5 stars, last pushed 2mo ago), with no licence file. It adds 54 tokens to every session and 4,942 once invoked, about $0.0003 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 skills, from other repositories
dspy
DSPy: declarative LM programs, auto-optimize prompts, RAG.
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
llm-security
Use for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.
ai-product
Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
llm-ops
LLM Operations -- RAG, embeddings, vector databases, fine-tuning, prompt engineering avancado, custos de LLM, evals de qualidade e arquiteturas de IA para producao.