trip-plan skillA
trip-plan is agent-read markdown (skill) from nano-muse/nanomuse: Plan a trip end to end — itinerary by day, a packing list to tick off, a budget, and the calendar checked for conflicts — as pages in the workspace. Use when the user is going somewhere for more than a day and wants a plan, an itinerary or a packing list..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Trip plan Everything goes in `trips/<place>-<yyyy-mm>/` in the workspace: `itinerary.html`, `packing.html`, and `budget.csv` when money is discussed. ## Before anything - You need: where, the dates (or roughly when and for how long), who is going, and what the trip is for (work, holiday, visiting someone). Ask for what is missing with **one** `ask_user` call — not one question at a time. - `recall` the user's travel preferences (pace, budget, dietary needs, kids, mobility, what they hated last time). Follow them without asking again. - `calendar` action=search for the trip dates: anything already on the calendar during the trip is a conflict to mention up front. ## Research - `web_search` for: how to get there and around, the weather in that season, opening days of the two or three things worth seeing, and anything that must be booked ahead. Two or three searches, then stop; `web_fetch` a page only when the search result is not enough. - Prices and times only from pages you actually read. If you did not find something, say "check" next to it rather than inventing a figure. …
Read the whole file at its exact version.
How to install
mdr add nano-muse/nanomuse/trip-plan@v1mdr add nano-muse/nanomuse/trip-plan@sha256:c721b23777211741Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3vcmjj3giph2zyu5)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1 latest | 2026-09-23 | 94f3cf2 | 3,491 B | A | view · diff |
| v1 | 2026-09-23 | f594033 | 3,177 B | A | view · diff |
| v1 | 2026-09-23 | 722b08a | 2,904 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3491 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nano-muse/nanomuse · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3vcmjj3giph2zyu5 GET https://markdownregistry.com/api/v1/resolve?ref=nano-muse/nanomuse/trip-plan GET https://markdownregistry.com/api/v1/blob/c721b2377721174153571b11439080b298bf738ddbab6c786333b6bed042385c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.