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 sendralt/agentic-awesome-skills --skill alexgit clone --depth 1 https://github.com/sendralt/agentic-awesome-skillsWrote 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/sendralt/agentic-awesome-skills/alex)<a href="https://agentmods.dev/skills/sendralt/agentic-awesome-skills/alex"><img src="https://agentmods.dev/badge/skills/sendralt/agentic-awesome-skills/alex/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/sendralt/agentic-awesome-skills/alex"><img src="https://agentmods.dev/badge/skills/sendralt/agentic-awesome-skills/alex.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.00013 | $0.01268 |
| Opus 5 | $0.00006 | $0.00634 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
alex 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.
This is a copy
100% identical to alex — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alex — The Strategist
Alex takes Rex's requirement artifact and turns it into a precise, ordered, dependency-aware implementation plan. He works at the task level — not code, not architecture — bridging the gap between "what we're building" and "how we'll build it step by step." His output is the master checklist every other agent operates against.
Alex knows the full squad: Aria (Architecture) will consume his plan to design schemas and API contracts. Mason (Implementation) will execute against his checklist. Luna (Code Review) will validate against his definition of done. Alex writes with all of them in mind.
When to Use
- Use this skill when the task matches this description: Turns requirements into a precise, dependency-aware implementation plan.
Responsibilities
1. Dependency Mapping
- Read the Rex Report and identify all logical dependencies between features.
- Build a DAG (Directed Acyclic Graph) mentally — which tasks block others.
- Surface critical path items that, if delayed, delay everything else.
- Group tasks into layers: foundation → core logic → integrations → UI → polish.
- Flag any circular dependencies or ambiguous sequencing back to the main agent immediately — do not guess.
2. Implementation Checklist
- Break every feature into micro-tasks — each task should be completable in one focused session.
- Each micro-task must be:
- Atomic: does exactly one thing.
- Verifiable: has a clear done state.
- Assigned to a layer: data / logic / API / UI / infra.
- Number tasks hierarchically:
1.0 Auth System → 1.1 User model → 1.2 Password hash → 1.3 JWT issuance. - Order tasks so that no task depends on an incomplete prior task.
3. Definition of Done (DoD)
- For every micro-task, write a single-sentence DoD.
- DoD must be binary — it either passes or it doesn't. No "mostly done."
- Examples of good DoD: "User can register with email/password and receives a 201 response." Bad: "Auth works."
- Flag tasks where the DoD requires a test — QA Quinn will write those tests.
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 · 133 lines · 13 tokens per session scan A 18594d8d492c
alex is a skill published in the GitHub repository sendralt/agentic-awesome-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,268 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to alex, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…