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 allemaar/open-skills --skill insight-exploregit clone --depth 1 https://github.com/allemaar/open-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/allemaar/open-skills/insight-explore)<a href="https://agentmods.dev/skills/allemaar/open-skills/insight-explore"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-explore/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/allemaar/open-skills/insight-explore"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-explore.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.00091 | $0.00817 |
| Opus 5 | $0.00046 | $0.00409 |
| Sonnet 5 | $0.00018 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
insight-explore 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/explore
Divergent thinking — generate 3+ implementation options, then converge on a recommendation. Produces options, not plans.
Structured execution spec:
protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
Brainstorming Protocol — explore before committing.
/insight-exploregenerates alternatives (divergent)./insight-assessevaluates them (convergent)./plan-createdesigns the chosen approach.
Phase 1 — Divergence
- Analyze constraints — what are we optimizing for? What are the hard requirements vs. preferences?
- Option A: The Standard Pattern — the obvious, well-trodden approach. What would most engineers reach for first?
- Option B: The Performance Way — optimized for speed, scale, or efficiency. Possibly more complex.
- Option C: The Minimalist — YAGNI. Smallest footprint that still solves the problem.
Additional options may be added if the problem space warrants them (e.g., event-driven, type-safe, or zero-dependency variants).
Phase 2 — Convergence
Compare all options across:
- DX — developer experience, API ergonomics, debuggability
- Robustness — error handling, edge case coverage, failure modes
- Timeline fit — how long does each take to implement and validate?
- Alignment — does it match existing patterns and coding standards in the repo?
Phase 3 — Recommendation
Output:
- Winner — which option and why
- Reason — 1–2 sentences, referencing the comparison
- Next step — ask the user: "Shall I
/plan-createthis?"
Rules
- MUST generate at least 2 distinct options (3 is the target).
- MUST NOT write code or make changes — this is ideation only.
Next Steps
/insight-assess— evaluate the winner in depth before committing/plan-create— design the chosen approach
Human output. This skill's handler-facing output obeys the human-output contract (
human-output/SKILL.md).
What ships with it
1 file 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 · 72 lines · 91 tokens per session scan A 48f11ff4ffa4
insight-explore is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed 23d ago), licensed Apache-2.0. It adds 91 tokens to every session and 817 once invoked, about $0.0005 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
polis-protocol
Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…
media
Skill "media" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
_data
Skill "_data" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.