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 status-reportgit 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/status-report)<a href="https://agentmods.dev/skills/shiwenwen/hope-agent/status-report"><img src="https://agentmods.dev/badge/skills/shiwenwen/hope-agent/status-report/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/status-report"><img src="https://agentmods.dev/badge/skills/shiwenwen/hope-agent/status-report.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.00048 | $0.01698 |
| Opus 5.5 | $0.00019 | $0.00679 |
| Sonnet 5.5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
status-report 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Report
When to Use
Trigger phrases: "weekly update", "monthly report", "status report", "project update", "1:1 prep", "周报", "月报", "工作汇报".
Match the cadence implied by the request:
- Daily / standup: 3 bullets max, "yesterday / today / blockers"
- Weekly: full template below
- Monthly: weekly template + "themes" section + metrics over time
- Quarterly / OKR: include progress against named goals + risk assessment
This skill optimizes for the reader's time, not yours. A status report is read in 60 seconds or skipped.
The Weekly Template
# <Your Name / Team Name> — Week of <YYYY-MM-DD>
## TL;DR
<2 sentences. What's the state of the world? Use plain English.>
## ✅ Shipped This Week
- <bullet — outcome, not activity. Link if relevant.>
- <bullet — outcome.>
## 🔄 In Flight
- <project> — <what stage, expected ship date>
- <project> — <what stage, expected ship date>
## ⚠️ Risks / Blockers
- <risk> — <impact + what's needed to unblock>
## 📊 Metrics (optional)
| Metric | This Week | Last Week | Δ |
|--------|-----------|-----------|---|
| <name> | <value> | <value> | <±> |
## 📅 Next Week
- <top 3 priorities, in order>
Workflow
-
Gather inputs via
recall_memory(if scope=session/project) andask_user_question:- Date range covered (default: last 7 days)
- Audience (manager? cross-functional? company all-hands?) — affects depth and jargon
- Key projects to cover
- Whether metrics are required and what the baseline is
-
Categorize ruthlessly — every bullet must fit exactly one bucket:
- Shipped = merged / launched / delivered / decided. Past tense.
- In Flight = work in progress, not yet shipped. Has an ETA.
- Risks/Blockers = something that will hurt the plan if not addressed. Has a specific owner ask.
-
Write outcomes, not activity:
- Bad: "Worked on auth migration. Had 3 design meetings."
- Good: "Auth migration: design approved, infra ready. Cutover scheduled for May 5 (low risk)."
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 · 183 lines · 48 tokens per session scan A a4b5cf62fab5
status-report is a skill published in the GitHub repository shiwenwen/hope-agent (1,860 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,698 once invoked, about $0.0002 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
issue-hygiene
How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.
aetox-slice
Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…
action-items
Manage your private to-do list for the user. Use to add or update tasks, record what they are waiting on, track blockers, mark tasks complete or canceled, and clean up the list. Not for Dreamers or external task trackers.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
notion
Search, read, create, and update Notion pages via the Notion MCP.
todoist
Read and manage Todoist tasks, projects, comments, labels, filters, and reminders through Todoist's official MCP server.