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 rana/skills --skill tomorrowgit clone --depth 1 https://github.com/rana/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/rana/skills/tomorrow)<a href="https://agentmods.dev/skills/rana/skills/tomorrow"><img src="https://agentmods.dev/badge/skills/rana/skills/tomorrow/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/rana/skills/tomorrow"><img src="https://agentmods.dev/badge/skills/rana/skills/tomorrow.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.00041 | $0.00412 |
| Opus 5.5 | $0.00016 | $0.00165 |
| Sonnet 5.5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
tomorrow 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 1mo 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
Examine the codebase, recent changes, and project documents.
Tomorrow Notes
Capture what future-you needs to know:
- The non-obvious — What code looks wrong but is actually correct? What workarounds exist and why? What would you "fix" if you didn't know the context?
- Magic values — Numbers, strings, thresholds, or timeouts that look arbitrary but have specific reasons. Document the reason, not just the value.
- Implicit ordering — Things that must happen in a specific order but nothing enforces it. Initialization sequences, migration steps, deployment procedures.
- Fragile spots — Code that works but will break if touched the wrong way. Areas where a reasonable-looking change would cause subtle bugs.
- Context that will evaporate — Why was this approach chosen over the obvious alternative? What did you try that didn't work? What constraints existed that might not be apparent?
- Dependency knowledge — Library quirks, API behaviors, platform-specific gotchas that you learned the hard way.
- The dragons — Areas where "here be dragons" is the honest documentation. What should future-you approach with extreme caution?
Focus area: $ARGUMENTS
For every note:
- What the thing is
- Why it matters (what breaks or confuses without this knowledge)
- Where to put the note (inline comment, CLAUDE.md, dedicated doc)
Present as an action list of notes to add. No changes to files — document only.
Output
Order by "what would confuse future-you most." State the total count when complete.
What questions would I benefit from asking?
What am I not asking?
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.
- 1mo ago First seen · 37 lines · 41 tokens per session scan A 198f098ae590
tomorrow is a skill published in the GitHub repository rana/skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 412 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
decision
Single entry point for all decision operations: capture, search, manage. Routes based on natural language intent.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…
delegate
Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.