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/proxy2021/enso/golden_hour_plannernpx skills add Proxy2021/Enso --skill golden_hour_plannergit clone --depth 1 https://github.com/Proxy2021/EnsoWrote 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/proxy2021/enso/golden_hour_planner)<a href="https://agentmods.dev/skills/proxy2021/enso/golden_hour_planner"><img src="https://agentmods.dev/badge/skills/proxy2021/enso/golden_hour_planner.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.00056 | $0.00923 |
| Opus 5 | $0.00028 | $0.00462 |
| Sonnet 5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
golden_hour_planner 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golden Hour Planner: plan photography trips around golden/blue hour timing, create shot planning cards with lighting/lens/subject details, track shooting streaks and weekly progress, access camera settings cheat sheets and composition guides, and run One Lens Challenge sessions.
Tool Reference
enso_ghp_plan_trip (primary)
Calculate golden hour, blue hour, sunrise, and sunset windows for a travel destination across your trip dates. Shows a daily shooting schedule with pre-dawn scout time, morning/evening golden hours, blue hours, and midday rest periods. Use when the user says: 'plan golden hour trip', 'golden hour schedule for my trip', 'photography trip planner'.
Parameters:
city(string): Destination city namestartDate(string): Trip start date (YYYY-MM-DD)endDate(string): Trip end date (YYYY-MM-DD)locations(string): Comma-separated list of key locations to photograph
enso_ghp_manage_shots
Create and manage shot planning cards for your trip. Each card tracks location, best time of day, focal length, subject type, light direction, and completion status (scouted/attempted/got the shot). Use when the user says: 'plan my shots', 'add shot card', 'shot planning', 'manage shot list'.
Parameters:
action(string): Action: load, add, update, delete, toggle_scouted, toggle_attempted, toggle_got_itcity(string): Destination city for this shot planshotId(string): Shot ID for update/delete/toggle actionslocation(string): Location name for the shotbestTime(string): Best time: morning_golden, evening_golden, blue_hour, midday_okfocalLength(string): Planned focal length: 28mm, 35mm, 50mm, 85mm+subjectType(string): Subject: architecture, portrait, street, landscape, culturelightDirection(string): Light direction: front_lit, side_lit, back_lit, silhouettenotes(string): Additional notes for this shot
enso_ghp_weekly_review
Weekly review dashboard showing shots planned vs attempted vs completed, golden hour session streak, and motivational tips from elite photographers. Use when the user says: 'weekly review', 'shooting stats', 'how am I doing', 'golden hour streak'.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 60 lines · 56 tokens per session scan A 187319613bf8
golden_hour_planner is a skill published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 923 once invoked, about $0.0003 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-31.
Other skills, from other repositories
speckit-specify
Create or update the feature specification from a natural language feature description.
speckit-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
add-sample
Create a SamplesApp sample page with correct theming and attributes. Use when adding UI samples for controls.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-git-remote
Detect Git remote URL for GitHub integration.
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.