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 ooocooc/open-skill-sunset --skill platform-specific-pathsgit clone --depth 1 https://github.com/ooocooc/open-skill-sunsetWrote 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/ooocooc/open-skill-sunset/platform-specific-paths)<a href="https://agentmods.dev/skills/ooocooc/open-skill-sunset/platform-specific-paths"><img src="https://agentmods.dev/badge/skills/ooocooc/open-skill-sunset/platform-specific-paths/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/ooocooc/open-skill-sunset/platform-specific-paths"><img src="https://agentmods.dev/badge/skills/ooocooc/open-skill-sunset/platform-specific-paths.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00112 |
| Opus 5.5 | $0.00008 | $0.00045 |
| Sonnet 5.5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
platform-specific-paths 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
Platform-specific paths
Run Q:\skill-sunset-fixture\runtime\example.exe.
Install dependencies with Q:\skill-sunset-fixture\runtime\package-tool.exe.
Load Q:\skill-sunset-fixture\references\config.md.
Validate with Q:\skill-sunset-fixture\scripts\check.example.
Write the report to Q:\skill-sunset-fixture\output\report.json.
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 · 13 lines · 19 tokens per session scan A 3813874d7d12
platform-specific-paths is a skill published in the GitHub repository ooocooc/open-skill-sunset (79 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 112 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-03.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
chromium-debug-use
Attach to a user's already-open Chromium-family browser for live inspection and light interaction after explicit local approval.
kimi-webbridge
A way for an AI agent to control the user's real web browser, including pages where the user is already signed in. It can navigate, click, type, read page content, and take screenshots.
browser-qa
Test live web interfaces with browser automation for smoke failures, interactions, visual regressions, responsive behavior, and accessibility. Use after frontend changes or deployments, during UI review, and before shipping critical user journeys.
browser-automation
Use when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page. Covers two providers (agent-browser local CLI, agentic-browser cloud) and the shared @e ref workflow.
research-agent
Use for current web/X research, library/API verification, competitive analysis, source-backed technical decisions, or updating docs with recent facts.