OpenMOSS is an operating system for teams of AI agents: it organizes agents into roles that plan, execute, review, and monitor work autonomously. It is for running recurring, multi-step tasks with little or no human coordination. The catalogue skills and agents extend the team’s abilities and workflows.
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 uluckyXH/OpenMOSS --skill local-web-searchgit clone --depth 1 https://github.com/uluckyXH/OpenMOSSWrote 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/uluckyxh/openmoss/local-web-search)<a href="https://agentmods.dev/skills/uluckyxh/openmoss/local-web-search"><img src="https://agentmods.dev/badge/skills/uluckyxh/openmoss/local-web-search/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/uluckyxh/openmoss/local-web-search"><img src="https://agentmods.dev/badge/skills/uluckyxh/openmoss/local-web-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 19 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 23 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00072 | $0.00387 |
| Opus 5 | $0.00036 | $0.00193 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
local-web-search 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 10d 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
Local Web Search (local-160)
Use the local Responses API with web_search to get web results and citations.
Quick start
- Ensure env vars are set or Keychain entries are configured (see
references/CONFIG.md). - Run the script:
/usr/bin/python3 {baseDir}/scripts/local_web_search.py --query "<your query>" --mode live
Optional (explicit .env path):
/usr/bin/python3 {baseDir}/scripts/local_web_search.py \
--env-file ~/.openclaw/workspace/.env \
--query "<your query>" \
--mode cached
Timeout default is 1200s. Override via --timeout or LOCAL_160_TIMEOUT.
Note: web_search responses can be slow; 5–10 minutes is common and up to ~20 minutes is possible. Don’t treat it as failure unless it exceeds your timeout.
Output handling
- Default output: one-sentence summary + up to 5 citations.
- Use
--jsonwhen you need full tool output for parsing. - Use
--mode live|cached|disabledto control external web access.
When to use
- For web lookups when local-160 supports
web_search. - For scheduled news monitoring that should use local-160 search.
Troubleshooting
- 401/403: key missing/invalid.
- 5xx: local gateway down or base URL wrong.
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.
- 10d ago First seen · 46 lines · 72 tokens per session scan A ae5199f72add
local-web-search is a skill published in the GitHub repository uluckyXH/OpenMOSS (1,322 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 387 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…