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/flurdy/agent-skills/landscapenpx skills add flurdy/agent-skills --skill landscapegit clone --depth 1 https://github.com/flurdy/agent-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/flurdy/agent-skills/landscape)<a href="https://agentmods.dev/skills/flurdy/agent-skills/landscape"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/landscape.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.00045 | $0.07143 |
| Opus 5 | $0.00023 | $0.03571 |
| Sonnet 5 | $0.00009 | $0.01429 |
| Haiku 4.5 | $0.00005 | $0.00714 |
Grade A, and why
landscape 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 5d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landscape — Morning Catch-up
Show a consolidated landscape of where you are and what to do next, pulling from multiple sources at once. Designed for the start of a work session (especially Monday mornings) to quickly orient.
Usage
/landscape # Full landscape
/landscape quick # Skip PR details (faster, Jira + working-copy + beads-if-present only)
What It Shows
Separate blocks, rendered from broadest context to most immediate. Order matters — the last block is the most load-bearing for "what am I doing right now":
- 📋 Jira — tickets assigned to you, not Done (with sprint and latest discussion)
- 🔀 PRs — org-wide open PRs, recently closed, unresolved threads
- 🎯 Beads — in-progress and top ready beads in this repo (skipped if
bdnot installed) - 📍 Working copy — current branch and uncommitted/unpushed work; at a multi-repo workspace root this becomes one per-repo table over every member instead, since the root's own branch is never where the work is
- Next — single-sentence suggestion for the most load-bearing action
Each block is independent — if one source fails, the others still render.
Instructions
MUST re-fetch on every invocation. Each
/landscaperun MUST execute every fetch from scratch —date, the Jira MCP query, thegh-pr-list-*andgh-pr-details.shscripts,beads.sh, andworking-copy.sh. NEVER reuse output from a previous run in the same session and NEVER extrapolate timestamps. State changes (PR merges, new approvals, ticket transitions) happen between runs; reusing stale tables has caused real merges to be missed in/pr-statusand the same risk applies here.MUST use the dedicated helper scripts. Never construct ad-hoc
bd …orgit …shell pipelines for this skill. Specifically: do NOT chaincommand -v bdprobes withbd list … && …or… || bd list --readyinside a single Bash call. Always invoke~/.agents/skills/landscape/scripts/beads.shinstead — it handles probing, repo gating, and listing internally. Likewise, do NOT hand-walk sibling service repos with your ownfor … git -C …loop — always go through~/.agents/skills/wrap-up/scripts/multirepo.sh(§4b), which handles workspace detection and per-repo state. Inline chaining bypasses the per-script permission allowlist and produces noisy permission prompts.
What ships with it
2 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.
- 5d ago First seen · 414 lines · 45 tokens per session scan A 9394fbf2d5de
landscape is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 7,143 once invoked, about $0.0002 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.