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 zeenie-ai/OpenCompany --skill progressive-discovery-skillgit clone --depth 1 https://github.com/zeenie-ai/OpenCompanyWrote 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/zeenie-ai/opencompany/progressive-discovery-skill)<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/progressive-discovery-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/progressive-discovery-skill/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/zeenie-ai/opencompany/progressive-discovery-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/progressive-discovery-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 179 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 181 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00020 | $0.01455 |
| Opus 5 | $0.00010 | $0.00727 |
| Sonnet 5 | $0.00004 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
progressive-discovery-skill 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 12d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progressive Tool Discovery
You are an agent that discovers and uses capabilities progressively as needed, rather than loading everything upfront.
Why Progressive Discovery?
Loading all tools at start creates:
- Token overhead: 150,000+ tokens for tool definitions
- Context pollution: Irrelevant tools confuse the LLM
- Slower responses: More tokens = more processing time
Progressive discovery provides:
- 98.7% token savings (Anthropic MCP research)
- Focused context: Only relevant tools loaded
- Better decisions: Less noise, clearer choices
Discovery Pattern
┌─────────────────────────────────────────────────────────────┐
│ PROGRESSIVE DISCOVERY │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. START with minimal context │
│ │ │
│ ▼ │
│ 2. IDENTIFY what capability is needed │
│ │ │
│ ▼ │
│ 3. CHECK what tools/agents are connected │
│ │ │
│ ├──▶ Tool exists? ──▶ USE it directly │
│ │ │
│ └──▶ Specialized agent exists? ──▶ DELEGATE to it │
│ │
│ 4. EXECUTE with focused context │
│ │ │
│ ▼ │
│ 5. RETURN result (don't load more than needed) │
│ │
└─────────────────────────────────────────────────────────────┘
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.
- 12d ago First seen · 225 lines · 20 tokens per session scan A 1b0703f44f23
progressive-discovery-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (880 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,455 once invoked, about $0.0001 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
browser-automation
Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
imsg
Use the imsg CLI from OpenClaw agents for iMessage/SMS DMs, groups, replies, reactions, polls, watching, and private-API actions.
acp-router
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read…
coding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
control-ui
Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.