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 odarino/haren --skill read-contextgit clone --depth 1 https://github.com/odarino/harenWrote 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/odarino/haren/read-context)<a href="https://agentmods.dev/skills/odarino/haren/read-context"><img src="https://agentmods.dev/badge/skills/odarino/haren/read-context.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.00016 | $0.00691 |
| Opus 5 | $0.00008 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
read-context 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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Context
Orient yourself at the start of every session or before taking any action.
Process
-
Read manifest.yaml
- Project name, mode, repos, sources
- Validate repo paths exist (warn if not)
-
Read progress.json
- List all modules and their current status
- List all features and their status within active modules
-
Read artifact-index.md
- Understand what artifacts exist
- Note any gaps (e.g., module has no plan yet)
-
Scan
artifacts/00-baseline/- List any files found (PDFs, docs, markdown, etc.)
- If files exist and mode is
undecided: → Suggest switching toblueprintmode ("You have baseline docs — blueprint mode is recommended") - If files exist and mode is
explore: → Suggest switching toblueprintmode ("Found docs in baseline — did you mean to use blueprint mode?") - If files exist and discovery hasn't started yet: → Suggest starting the discover phase to process them
- If files were added since last session (compare against artifact-index.md): → Flag new documents and ask if the user wants to re-run or update discovery
-
Git check (for each repo in manifest)
- Check for uncommitted changes
- Compare last known commit in progress.json against actual HEAD
- If drift detected: warn user, update progress.json to match git
-
Produce orientation summary
Output Format
Present to the user:
## Session Context
Project: {name} ({mode} mode)
Iteration: {N} of {total} ({status}) ← only if iterations enabled
Repos: {list with status}
## Baseline Documents
{list of files in 00-baseline/, or "None"}
{if new docs found: "⚠ New documents detected since last session"}
## Module Status
- {module}: {STATUS} ({detail — e.g., "3/7 tasks done"})
- If status is "planned" or "planning":
- If iterations disabled: check which files exist in 04-plans/{module}/
- ✓ spec.md | ✗ spec.md
- ✓ design.md | ✗ design.md
- ✓ tasks.md | ✗ tasks.md
- If iterations enabled: check master and active iteration plan
- Master: ✓ spec.md | ✗ spec.md, ✓ design.md | ✗ design.md
- Iteration {N}: ✓ spec.md | ✗ spec.md, ✓ design.md | ✗ design.md, ✓ tasks.md | ✗ tasks.md
- ...
## Suggested Next Action
{what to do next based on current state}
## Active Blockers
{any blocked features or modules}
## Recent Events
{last 5 entries from events/events.jsonl}
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.
- 7d ago First seen · 85 lines · 16 tokens per session scan A 0219382ad9fb
read-context is a skill published in the GitHub repository odarino/haren (11 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 691 once invoked, about $0.0001 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
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.