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-skill-gapgit 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-skill-gap)<a href="https://agentmods.dev/skills/allemaar/open-skills/insight-skill-gap"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-skill-gap/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-skill-gap"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-skill-gap.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.00076 | $0.00873 |
| Opus 5 | $0.00038 | $0.00436 |
| Sonnet 5 | $0.00015 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
insight-skill-gap 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 11d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-gap
Identify gaps in the skill library based on recent implementation work — propose new skills or updates to existing ones.
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.
Skill Discovery Protocol — ensures reusable patterns don't stay buried in implementation code.
Phase 1 — Recent Work Scan
- Gather recent context — conversation history, changed files, new patterns introduced. Summarize: what was built, which libraries/frameworks were used, what novel patterns emerged.
- Load skill index — read the current skill index to know what already exists before analyzing gaps.
Phase 2 — Gap Analysis
Cross-reference patterns from Phase 1 against the skill index. Classify each pattern:
- (A) Skill exists and covers it — no action
- (B) Skill exists but is incomplete — propose update; specify which sections are missing or outdated
- (C) No skill exists — evaluate against new-skill criteria below
Criteria for a new skill:
- Pattern is reusable (used 2+ times, or clearly will be)
- Pattern involves non-obvious decisions or gotchas
- Pattern spans multiple files or concepts
Gate: gap analysis must be documented before proceeding.
Phase 3 — Skill Proposals
For each gap, draft a skill specification:
- Skill name — domain-prefix convention (e.g.,
drizzle-*,nextjs16-*) - Skill family — domain prefix
- Prerequisites — what the user needs to know first
- Complexity estimate — how large/involved the skill content will be
- Key sections to cover — what the skill should teach
Check new-skill-creator for template requirements before drafting. Present proposals to the user and wait for approval before proceeding.
Phase 4 — Execution (only if approved)
Create approved skills via /new-skill-creator. For updates, apply targeted edits to the relevant sections.
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.
- 11d ago First seen · 82 lines · 76 tokens per session scan A a1a7bc00966b
insight-skill-gap is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 873 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
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.