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 iradoweck/antigravity-awesome-skills --skill alexgit clone --depth 1 https://github.com/iradoweck/antigravity-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/iradoweck/antigravity-awesome-skills/alex)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/alex"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-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/iradoweck/antigravity-awesome-skills/alex"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-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.01353 |
| Opus 5.5 | $0.00005 | $0.00541 |
| Sonnet 5.5 | $0.00003 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00135 |
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 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.
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 — 138 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 when converting confirmed requirements into ordered milestones, dependencies and verifiable acceptance criteria.
Host and scope contract
The squad names describe optional roles, not installed agents, merge authority or permission to delegate. Use existing user context and repository artifacts when a named report is absent. Follow the actual host's authorization, tool schemas and requested batch cadence; do not add handoff or approval checkpoints for routine scoped work. Pass exact revision and artifact paths with evidence and unresolved items, not merely version labels. Keep private data and secrets out of reports.
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.
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 Changed · +5 lines da18cca5e7d8
- 1mo ago First seen · 133 lines · 13 tokens per session scan A 18594d8d492c
alex is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 1,353 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.