Awesome AI Apps is a collection of 132 projects, tutorials, and recipes for building applications powered by large language models. Developers use it to explore text and voice agents, retrieval-augmented generation, workflows, MCP tools, memory, and fine-tuning.
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 agentmods add skills/arindam200/awesome-ai-apps/write-postnpx skills add Arindam200/awesome-ai-apps --skill write-postgit clone --depth 1 https://github.com/Arindam200/awesome-ai-appsWrote 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/arindam200/awesome-ai-apps/write-post)<a href="https://agentmods.dev/skills/arindam200/awesome-ai-apps/write-post"><img src="https://agentmods.dev/badge/skills/arindam200/awesome-ai-apps/write-post.svg" alt="Measured on agentmods" 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.00106 | $0.00433 |
| Opus 5 | $0.00053 | $0.00217 |
| Sonnet 5 | $0.00021 | $0.00087 |
| Haiku 4.5 | $0.00011 | $0.00043 |
Grade A, and why
write-post 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- write-post — 100% identical, 0 lines differ
What it actually says
Write LinkedIn Post
Generate a LinkedIn post using the linkedin-writer MCP server.
Working Directory
All output goes into outputs/{slug}/ relative to the project root. Derive the slug from:
- The dataset seed/guideline filename if the user references one (e.g.,
my-topic_seed.md→my-topic) - Otherwise, slugify the topic (lowercase, hyphens, no special chars, max 60 chars)
Create the directory if it doesn't exist.
Input Preparation
The working directory needs guideline.md and research.md.
If the user provides raw text for the guideline, create guideline.md in the working directory:
# LinkedIn Post Guideline
## Topic
[What the post is about]
## Angle
[What perspective or approach to take]
## Target Audience
[Who this post is for]
## Key Points to Cover
[3-5 bullet points]
## Tone
[How it should sound]
If research.md is in a different location, copy it into the working directory.
Execution
Read the WORKFLOW_INSTRUCTIONS from src/writing/routers/prompts.py and follow those steps exactly, using the linkedin-writer MCP tools. Pass outputs/{slug}/ as the working directory path to each tool.
After Completion
Present the final outputs/{slug}/post.md content to the user. If an image was generated, mention outputs/{slug}/post_image.png.
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.
- 6d ago First seen · 52 lines · 106 tokens per session scan A a171ed0c5005
write-post is a skill published in the GitHub repository Arindam200/awesome-ai-apps (13,677 stars, last pushed 6d ago), licensed MIT. It adds 106 tokens to every session and 433 once invoked, about $0.0005 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-30.
Other skills, from other repositories
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
benchmark-tune
Use this skill when running, debugging, interpreting, or documenting mesh-llm benchmark tune model-serving throughput trials, including choosing ctx/batch/ubatch/mmap/mlock/speculative-decoding sweeps, running benchmark tune on local or SSH hosts, collecting JSON evidence, and applying tolerance-aware recommendations.…
deploy-windows
Use this skill when installing, deploying, launching, serving, or troubleshooting mesh-llm on a Windows machine — PowerShell install via install.ps1, flavor selection (CUDA/ROCm/Vulkan/CPU), source builds, the contrib helper scripts, and verifying it serves.
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.