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 roarista/awesome-harness --skill orientgit clone --depth 1 https://github.com/roarista/awesome-harnessWrote 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/roarista/awesome-harness/orient)<a href="https://agentmods.dev/skills/roarista/awesome-harness/orient"><img src="https://agentmods.dev/badge/skills/roarista/awesome-harness/orient.svg" alt="Measured on agentmods" 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.00139 | $0.02288 |
| Opus 5 | $0.00069 | $0.01144 |
| Sonnet 5 | $0.00028 | $0.00458 |
| Haiku 4.5 | $0.00014 | $0.00229 |
Grade A, and why
orient 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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orient — recall + understand + gate, one skill
Steps 1-3 of THE PROCEDURE (
/awesomeharness): ORIENT(0) -> RECALL -> UNDERSTAND -> GATE -> DECOMPOSE -> BUILD -> VERIFY -> PERSIST. On BUILD, hand off tocode-decompose; on STOP, hand back to Ro.
Merges the old recall and codebase-first skills — they were sequential steps of one pipeline that nobody invoked separately (0 and 0 real invocations across 2,997 transcripts). One call now does the whole pre-code phase and ends in a single pasteable block.
Part A — RECALL (memgraph + mulch + MEMORY.md)
python3 ~/.claude/tools/memgraph/mem.py query "<topic from the task>"— ranked full-text hit(s); read the top hit(s),mem.py graph <name>to pull linked records if load-bearing.- In a repo with
.mulch/:ml search "<topic>"(orml primeat session start) for the repo's own decisions/conventions/failures — memgraph is Ro's global memory, mulch is this repo's. - Read budget: <=5 file reads. Hop card-by-card (
mem query-> top hit ->mem graphthe one linked record) rather than bulk-reading; if 5 reads don't answer it, narrow the query, don't widen the reads. - Heavy recall (many hits, need several full bodies) -> spawn ONE
Exploresubagent to run the queries and return only the synthesis. - Exit artifact: <=5 bullets (prior decisions, known failure modes, any
scaffold-<category>.md) — this is what feeds Part B as "prior art," not a transcript dump. - Missing index ->
python3 ~/.claude/tools/memgraph/build.pyfirst. Read-only; never mutate memory records as a side effect. Dangling[[links]]are expected TODOs, not errors.
Part B — UNDERSTAND (front door -> map -> reuse ladder)
Owns the missing middle: user goal -> front door/live state -> capability/reuse discovery -> proven gap -> decomposition. Does NOT own builder routing, code audit, or state handoff.
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.
- 6d ago First seen · 110 lines · 139 tokens per session scan A aa0545a3b6a1
orient is a skill published in the GitHub repository roarista/awesome-harness (1 stars, last pushed 11d ago), licensed MIT. It adds 139 tokens to every session and 2,288 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.