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 orient-gapsgit 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/orient-gaps)<a href="https://agentmods.dev/skills/allemaar/open-skills/orient-gaps"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/orient-gaps/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/orient-gaps"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/orient-gaps.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.00146 | $0.04530 |
| Opus 5 | $0.00073 | $0.02265 |
| Sonnet 5 | $0.00029 | $0.00906 |
| Haiku 4.5 | $0.00015 | $0.00453 |
Grade A, and why
orient-gaps 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orient-gaps
What is stuck or missing? Answers with — blockers (on you vs on others) · open forks · loose ends · inferred silent gaps · (
--audit) unbacked claims. Does not answer — how far along (/orient-status) · what changed (/orient-map) · what comes next (/orient-roadmap). Owns for the family — the stall surface and the anti-Goodhart audit tier.
Computes a fresh, honest read of what is stuck and what is missing — blockers, open forks, loose ends, and the inferred silent gaps — and returns it as one ephemeral bundle (a structured YON record + a human markdown read + a small visual). --audit adds a second tier: claim-vs-evidence mismatches and gamed-signal disclosure ("don't trust the orientation"). Part of the orient- family; emits the gaps slice of the shared record at references/orient-spec/orient-record.yon.
Structured execution spec:
protocol.yon. Read it for the canonical steps, rules, and gates; this file is the human-readable, self-sufficient explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
The shared record, render contract, worked fixtures, and value validator travel
inside references/. The repository-only round-trip guard is
release evidence; its absence from an installed copy does not block execution.
When to use
- "What's stuck / what's blocking / what's not done / what's missing" on a project, repo, plan, or task.
- Before trusting a status read — to see whether the bearings rest on anything solid.
--audit: "don't trust the orientation" — raise claims that lack evidence and metrics that look inflated.
How it works (self-sufficient — works without protocol.yon)
orient-gaps delegates the gathering to a bounded, read-only subagent so the calling session (a human's, or an agent orienting itself) never sees the search/inference noise — only the result bundle comes back. Nothing is stored; every call recomputes from current reality. The stall surface and the silent gaps are two tiers of one sweep; --audit raises a third.
What ships with it
9 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.
- protocol.yon 11 KB
- references/orient-spec/examples/bad/enum-banana.yon 2.0 KB
- references/orient-spec/examples/bad/fail-open.yon 1.6 KB
- references/orient-spec/examples/orient-record.example.yon 3.2 KB
- references/orient-spec/family-behaviors.md 9.9 KB
- references/orient-spec/family-manifest.yon 7.2 KB
- references/orient-spec/orient-contract.md 12 KB
- references/orient-spec/orient-record.yon 14 KB
- references/tools/orient-validate.mjs 14 KB runs code
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 · 160 lines · 146 tokens per session scan A 614dc9de1a12
orient-gaps is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed today), licensed Apache-2.0. It adds 146 tokens to every session and 4,530 once invoked, about $0.0007 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.