orient-status

orient-status is a skill for Claude Code from allemaar/open-skills. It costs 160 tokens per session (4,157 once invoked), scanned A, original, Apache-2.0.

A progress and time estimate tool for a project, folder, plan, or task. It reports where work stands, what remains, and a rough completion window.

In plain words
What is it for?
Use it to check project status, remaining work, estimated timing, or what to do next after losing context.
Why use it?
It gives you a fresh view of progress when the current state is unclear or you have returned after a break. A resume option helps rebuild the thread with one suggested next step.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Part of the open-skills plugin — 70 skills shipped together

Good fit Use it to check project status, remaining work, estimated timing, or what to do next after losing context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/allemaar/open-skills/orient-status
Install

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.

Any agent
npx skills add allemaar/open-skills --skill orient-status
Clone the repo
git clone --depth 1 https://github.com/allemaar/open-skills

Made for: Claude Code.

Or install open-skills, the plugin that ships this one along with the rest of its 70 skills.

Wrote 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.

agentmods badge for orient-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/allemaar/open-skills/orient-status/github.svg)](https://agentmods.dev/skills/allemaar/open-skills/orient-status)
Your own site
<a href="https://agentmods.dev/skills/allemaar/open-skills/orient-status"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/orient-status/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.

agentmods 80×15 button for orient-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/allemaar/open-skills/orient-status"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/orient-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00160 $0.04157
Opus 5 $0.00080 $0.02079
Sonnet 5 $0.00032 $0.00831
Haiku 4.5 $0.00016 $0.00416

Measured 12d ago against content hash 19b35e4fcdd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

orient-status 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.

The scan reads SKILL.md. This mod also ships 1 executable file (references/tools/orient-validate.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/orient-status/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/orient-status

How far along am I, and when will it be done? Answers with — position · what is left · a banded ETA · (--resume) the one next move. Does not answer — what changed (/orient-map) · what is stuck (/orient-gaps) · what comes next (/orient-roadmap). Owns for the family — nothing topological; it consumes /orient-map's topology fields.

Computes a fresh, honest read of where the current work stands — position, remaining work, and a banded ETA — and returns it as one ephemeral bundle (a structured YON record + a human markdown read + a small visual). --resume re-frames it for the "I just came back and lost the thread" case. Part of the orient- family; emits a 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 @STAMP date.

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

  • "Where are we / what's the status / how far along / what's the ETA" on a project, repo, plan, or task.
  • After a context fill or at the start of a session, before deciding the next move.
  • --resume: you've been away (a gap, a context-switch) and lost the thread — you need what changed + exactly where to put your hands next.

How it works (self-sufficient — works without protocol.yon)

orient-status 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.

Read the full file on GitHub · 148 lines

Changes

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.

  1. 12d ago First seen · 148 lines · 160 tokens per session scan A 19b35e4fcdd6

Subscribe to this mod's changes

orient-status is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 160 tokens to every session and 4,157 once invoked, about $0.0008 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.