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/onurpolat05/alba/setupnpx skills add onurpolat05/ALBA --skill setupgit clone --depth 1 https://github.com/onurpolat05/ALBAWrote 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/onurpolat05/alba/setup)<a href="https://agentmods.dev/skills/onurpolat05/alba/setup"><img src="https://agentmods.dev/badge/skills/onurpolat05/alba/setup.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 | $0.00113 | $0.03124 |
| Opus 5 | $0.00056 | $0.01562 |
| Sonnet 5 | $0.00023 | $0.00625 |
| Haiku 4.5 | $0.00011 | $0.00312 |
Grade A, and why
setup 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 3d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALBA Interactive Setup
Create a personalized AI agent system through collaborative discovery. Ask, don't assume.
Why
disable-model-invocation: true: this skill overwritesCLAUDE.md,.claude/settings.jsonand the wholememory/tree. Nothing here should ever fire because a prompt sounded vaguely like "help me get set up". The flag restricts it to an explicit/setupfrom the user, and it also keeps the skill out of scheduled-task triggers and out of subagent preloading — both places where an accidental run would be invisible until the damage was done.
Phase 1: Discovery (ask ONE question at a time)
Show progress with each question: "(1/7)", "(2/7)", etc.
Q1 - Role (1/7): "Let's build your ALBA agent! What's your primary role?" Options: Software Developer, Project Manager, Designer, Content Creator, Researcher, Business/Founder, Other
Q2 - Daily Work (2/7): "What takes up most of your time daily?" (allow multiple) Options: Writing/reviewing code, Managing projects, Communication, Research, Content creation, Email/calendar, Design, Other
Q3 - Pain Points (3/7): "What frustrates you most in your workflow?" Options: Too many tools, Email overload, Losing track of tasks, Repetitive work, Scattered info, Losing context, Other
Q4 - Tools (4/7): "Which tools do you use regularly?" (allow multiple) Options: GitHub, Trello, Notion, Gmail, Slack, Google Calendar, Linear, Obsidian, Other
Q5 - Automation Goals (5/7): "What would you like to automate or improve?" Free text or: Task organization, Email categorization, Research, Content creation, Team updates, Meeting notes
Q6 - Technical Level (6/7): "How comfortable are you with technical setup?" Options: Beginner (guide me), Intermediate (can edit configs), Advanced (full control)
Q7 - Setup Scope (7/7): "How do you want to start?" Options: Minimal (essentials only), Standard (recommended), Full (everything)
Phase 2: Create Structure
2a. Core Structure (always created)
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.
- 3d ago First seen · 268 lines · 113 tokens per session scan A 0685dfed49bc
setup is a skill published in the GitHub repository onurpolat05/ALBA (20 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 3,124 once invoked, about $0.0006 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
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.