Hope Agent is a cross-device personal AI assistant that remembers context, uses tools, and continues working toward goals through dynamically organized workflows. Individuals use it from desktop, web, server, or messaging environments to manage projects, knowledge, designs, and long-running tasks. The catalogue add-ons extend its agent workflows and capabilities.
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 shiwenwen/hope-agent --skill ha-knowledgegit clone --depth 1 https://github.com/shiwenwen/hope-agentWrote 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/shiwenwen/hope-agent/ha-knowledge)<a href="https://agentmods.dev/skills/shiwenwen/hope-agent/ha-knowledge"><img src="https://agentmods.dev/badge/skills/shiwenwen/hope-agent/ha-knowledge/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/shiwenwen/hope-agent/ha-knowledge"><img src="https://agentmods.dev/badge/skills/shiwenwen/hope-agent/ha-knowledge.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.00187 | $0.01736 |
| Opus 5.5 | $0.00075 | $0.00694 |
| Sonnet 5.5 | $0.00037 | $0.00347 |
| Haiku 4.5 | $0.00019 | $0.00174 |
Grade A, and why
ha-knowledge 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Space — operating method
Notes in a Hope Agent knowledge base are real .md files on disk — the
file is the single source of truth; the search index, link graph, and tags are a
rebuildable cache derived from it. Your job is to keep that corpus coherent: the
value of a knowledge base is in its links, not its file count.
The note_* tools only appear when a knowledge base is attached to the session.
If you don't see them, no KB is accessible — tell the user to attach one (in the
composer's KB picker, or project settings) rather than guessing.
The loop: orient → act → link
Before writing, orient. A blind note_create produces an orphan that no one
will ever find again. The discipline that separates a knowledge base from a pile
of files is: every new note gets wired into the graph in the same turn you
create it.
- Orient —
note_search(hybrid full-text + vector) for existing notes on the topic. For a known note,note_readreturns its content plus its links, backlinks, and tags in one call — read it before editing. - Act — create / edit (see tool guide below).
- Link — connect the new or changed note to what's already there
(
note_link, ornote_suggest_linksto find unlinked mentions). A note with zero links is an orphan; check withnote_orphansperiodically.
Tool selection — pick the narrowest tool
Reading / discovery
note_search— find notes by topic (hybrid FTS + semantic). Your default entry point.note_read— one note's full content + its links / backlinks / tags.note_similar— semantically nearest notes (vector KNN) to a given note.note_related— fused recall: backlinks ∪ out-links ∪ vector ∪ shared tags. Use when you want "everything connected to this", not just text matches.note_backlinks/note_by_tag/note_tags— graph + tag lookups.note_graph/note_orphans/note_broken_links— structural health.knowledge_recall— when you need both long-term memory and notes in one query. It keeps the two result sets separate; don't treat it as a notes-only search (usenote_searchfor that).
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.
- 1mo ago First seen · 122 lines · 187 tokens per session scan A e3cfcae35e44
ha-knowledge is a skill published in the GitHub repository shiwenwen/hope-agent (1,858 stars, last pushed yesterday), licensed MIT. It adds 187 tokens to every session and 1,736 once invoked, about $0.0007 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
memory-generation
A guide for deciding when the assistant should create a memory about something the user explicitly wants remembered or about a useful lesson.
self_awareness
Ground self-referential answers in the agent's actual filesystem. Use when the user asks who the agent is, what it can do, what it knows, what it remembers, what it has built, what services are connected, or what rules it follows.
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
consolidate-memory
Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.
technology-search
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.