Borrowing it
Nothing to install: this file belongs to kyleve/Stuff. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kyleve/Stuff/main/.agents/skills/update-explore-features/SKILL.mdgit clone --depth 1 https://github.com/kyleve/StuffWrote 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/kyleve/stuff/update-explore-features)<a href="https://agentmods.dev/skills/kyleve/stuff/update-explore-features"><img src="https://agentmods.dev/badge/skills/kyleve/stuff/update-explore-features/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/kyleve/stuff/update-explore-features"><img src="https://agentmods.dev/badge/skills/kyleve/stuff/update-explore-features.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.00035 | $0.00620 |
| Opus 5.5 | $0.00014 | $0.00248 |
| Sonnet 5.5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
update-explore-features 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Explore Features
Keep Settings > Explore Features useful for people who do not know every Where workflow. The default invocation updates local files. Leave changes uncommitted and do not push, publish a PR, or create a schedule. An explicit request for those actions overrides this default.
Find coverage gaps
- Read the root and WhereUI
AGENTS.mdfiles. - Read
Where/WhereUI/Sources/Settings/SettingsSearch.swiftand the galleries underFeaturePreviewsbeside it. - Compare the galleries with current release-facing screens, settings, widgets, App Intents, and the share extension.
- Use recent Git history to find changed behavior. Verify each claim against current source and tests.
Start with Locations, Your Year, recording, manual entries, corrections, evidence, planning, customization, and privacy controls. Follow source registrations to discover additional workflows. Do not treat this list or README prose as a complete feature catalog. Exclude developer tools and unimplemented backlog features.
Report each gap as a missing workflow, inaccurate claim, outdated visual, missing search entry, or broken action. Name the source that establishes the behavior. Do not maintain a second persistent coverage inventory.
Update the galleries
Use the building-ui skill and its companion SwiftUI guidance.
Extend an existing page when the topic belongs to its workflow.
Add a page only when the workflow needs its own explanation and visuals.
Keep core workflows before optional integrations in the Explore list.
Reuse production visual components and the existing gallery chrome. Keep browsing read-only. Do not start location requests, issue scans, exports, recording, or edits to render examples. Use injected state. Keep example data visibly distinct from actual records. Preserve honest empty, unavailable, and failed states. A zero issue count alone does not prove a completed scan. Hide action links whose destinations are unavailable in demo mode.
Read the current privacy presentation and backup contracts before writing claims about them. Privacy disclosures use process-effective settings. Backup import remains an onboarding flow. Keep topic titles, search focus items, navigation, Flyover registrations, previews, and snapshots together with each change. Use localized copy and typed symbols. Update module documentation when its described behavior changes.
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 · 56 lines · 35 tokens per session scan A 13ae233cc185
update-explore-features is a skill published in the GitHub repository kyleve/Stuff (4 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 620 once invoked, about $0.0001 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-27.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…