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/startnpx skills add onurpolat05/ALBA --skill startgit 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/start)<a href="https://agentmods.dev/skills/onurpolat05/alba/start"><img src="https://agentmods.dev/badge/skills/onurpolat05/alba/start.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.00109 | $0.00382 |
| Opus 5 | $0.00055 | $0.00191 |
| Sonnet 5 | $0.00022 | $0.00076 |
| Haiku 4.5 | $0.00011 | $0.00038 |
Grade A, and why
start 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.
What it actually says
/start - Session Start
Load context and show today's focus. Keep output under 10 lines.
Steps
- Read dashboard (silent):
memory/state/dashboard.md - Read todo (silent):
memory/state/todo.md - Check for resume: Look for
memory/daily/YYYY-MM-DD.md(today's date)
Output Format
Session: YYYY-MM-DD HH:MM
[If resuming: "Resuming - previous session logged"]
Priorities:
- [TOP priority from dashboard - most urgent/important item]
- [Secondary priority]
- [Next actionable step]
Tasks: X active | Y completed today
Rules
- Maximum 10 lines of output
- If dashboard doesn't exist yet, say: "No dashboard found. Run /setup first or create memory/state/dashboard.md"
- If todo doesn't exist, skip task count
- Don't read errors.md or learnings.md at start (save context window)
- Don't ask questions - this is a pure read-and-display command
- Use the user's language preference from CLAUDE.md (default: follow dashboard language)
- Show priorities by importance, not by file order
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 · 42 lines · 109 tokens per session scan A 079e3b7cb164
start is a skill published in the GitHub repository onurpolat05/ALBA (20 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 382 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
trellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
trellis-channel
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
start
Session initialization and lifecycle management: bootstraps session context, organizes files, generates CLAUDE.md, manages soul purpose lifecycle with completion protocol and active context harvesting. Use when user says /start, /init, bootstrap session, initialize session, or organize project.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
stop
Gracefully close, pause, or verify a session: harvest promotable content, save progress, archive soul purpose, settle AtlasCoin bounty. Use when user says /stop, wrap up, done for the day, finishing up, close session, pause, verify, or end session.