Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/victoriacity/openakari/main/.claude/skills/orient-simple/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/victoriacity/openakari/orient-simple)<a href="https://agentmods.dev/skills/victoriacity/openakari/orient-simple"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/orient-simple/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/victoriacity/openakari/orient-simple"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/orient-simple.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.00025 | $0.01337 |
| Opus 5.5 | $0.00010 | $0.00535 |
| Sonnet 5.5 | $0.00005 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
orient-simple 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orient-simple
Simplified orient skill for Fast Model and similar models. Select a task to work on in <3 turns.
When to use
At the start of every autonomous work session, before selecting a task.
Procedure
Execute these steps in order:
Step 1: Check for orphaned work
Run git status. If there are uncommitted changes that are project work (not scheduler state files), commit them with a descriptive message. Skip scheduler state files (.scheduler/, *.json in infra).
Step 2: Read TASKS.md files
Read all projects/*/TASKS.md files. For each task, note:
[ ]= open,[x]= done[in-progress: DATE]= someone is working on it, skip[blocked-by: ...]= cannot proceed, skip[approval-needed]= requires human approval, skip[zero-resource]= costs no budget resources
Step 3: Routing tag check
While reading TASKS.md files (Step 2), verify that [requires-opus] tags are applied correctly:
Tag [requires-opus] if ANY true:
- NOT self-contained (needs multi-file context beyond task text + project README)
- Unclear done-when condition (requires judgment to verify)
- Multiple concerns ("do X, then Y, then Z")
- Deep reasoning required (synthesis, strategic decisions, multi-step planning)
- Convention changes (modifies CLAUDE.md, decisions/, or infra/)
If your repo uses routing tags, untagged tasks may default to fleet-eligible. Only apply [requires-opus] when a task genuinely needs Opus-level capability.
Step 4: Task supply generation and decomposition (ADR 0047, ADR 0053)
If task supply is thin, improve it before proceeding. In repos that enable fleet execution, this also helps maintain fleet-ready task supply.
How to generate (in order):
- Remove stale
[blocked-by: ...]tags where the referenced condition is resolved (prerequisite task already completed) - Decompose
[requires-opus]tasks that have >2 independent steps, >3 files, or mix mechanical + judgment work. Split into smaller subtasks. Write subtasks directly to TASKS.md — replace the original task with its subtasks. Do NOT just flag or propose — proposals die with the session. - Create maintenance tasks:
Run /self-audit on <project>for projects that haven't been audited in the last 7 days. To check: runls projects/*/diagnosis/compliance-audit-*.md 2>/dev/null | xargs -I{} basename {}to list audit files. Extract dates from filenames (pattern: YYYY-MM-DD). Skip projects with audits within 7 days of today. - Create documentation or analysis tasks from standing inventory (see CLAUDE.md "Fleet supply maintenance")
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.
- 2mo ago First seen · 130 lines · 25 tokens per session scan A 644d3bf757c6
orient-simple is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 1,337 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…