Echo Agent is a self-hosted, long-running AI agent that connects language models, tools, memory, permissions, and messaging channels in one system. Individuals and teams use it for private automation that retains context across sessions, develops skills, schedules tasks, and requires approval for high-risk actions.
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 fuyuxiang/echo-agent --skill daily-briefinggit clone --depth 1 https://github.com/fuyuxiang/echo-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/fuyuxiang/echo-agent/daily-briefing)<a href="https://agentmods.dev/skills/fuyuxiang/echo-agent/daily-briefing"><img src="https://agentmods.dev/badge/skills/fuyuxiang/echo-agent/daily-briefing/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/fuyuxiang/echo-agent/daily-briefing"><img src="https://agentmods.dev/badge/skills/fuyuxiang/echo-agent/daily-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00646 |
| Opus 5.5 | $0.00010 | $0.00258 |
| Sonnet 5.5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
daily-briefing 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Briefing
The Agent can combine weather, tasks, news and calendar using the relevant skills. The helper script provides a smaller date/weather/reminder summary.
Agent composition recipe
The following is a planning recipe for the Agent, not a file automatically read by the script. The bundled script accepts only --city, prints date/weather/local reminders, and does not fetch calendar/news, send messages, or register a schedule:
schedule: "0 8 * * *" # 每天早上8点
location: Beijing
sections:
- weather
- reminders
- rss
- calendar
rss_feeds:
- https://hnrss.org/frontpage
- https://arxiv.org/rss/cs.AI
max_news: 5
channel: telegram # delivery channel
Briefing Template
☀ 每日简报 — {date}
## 天气
{location}: {condition} {temp}°C, 湿度 {humidity}%
## 今日待办
- [ ] {reminder_1}
- [ ] {reminder_2}
## 新闻摘要
1. {title_1} — {source}
2. {title_2} — {source}
## 日程
- 09:00 {event_1}
- 14:00 {event_2}
Script Usage
# Generate briefing now
python3 scripts/generate_briefing.py
# Select the weather city; output goes to stdout
python3 scripts/generate_briefing.py --city Beijing
Scheduling
Add to Echo Agent's cron channel for automatic daily delivery. The cron expression 0 8 * * * fires at 8:00 AM daily.
Create the job with the cronjob tool. If the briefing produces a file (e.g. a
voice version), deliver it inside the same run — for audio use
text_to_speech(..., deliver=true), for other files call send_file with the
target channel/chat. An unattended run may end right after generating the file,
so a "generate now, send later" split silently drops it.
After creating the job: confirm, then stop
When cronjob(action="create") returns, send the user ONE confirmation — job id,
schedule, next fire time — and end the turn. Do NOT "verify delivery" by reading
gateway/server.py / a2a/server.py or curling internal endpoints
(/v1/chat, /api/v1/message); that is not a delivery test, it just burns the
turn and leaves the user without a reply. To sanity-check, use
cronjob(action="list"); the scheduled fire is the real delivery.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -3 lines 61561487151b
- 1mo ago First seen · 85 lines · 25 tokens per session scan A 945bf3d6038b
daily-briefing is a skill published in the GitHub repository fuyuxiang/echo-agent (1,036 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 646 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
agent-state-bar
A design guide for an agent status bar: a short, automatically updated summary of progress, remaining tasks, tool counts, errors, and system state placed near the latest model input.
knowledge-org
A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.
context-compression
A guide to shortening the information an agent carries between steps. It explains how to replace large tool outputs and old conversation details with compact, useful summaries while preserving important decisions and constraints.
memory-system
A guide to giving an AI agent persistent, user-specific memory across conversations. It covers what to remember, how to store it, how to update or compress it, and when to use memory instead of a shared knowledge base.
dingtalk-message
A tool for sending DingTalk messages through either a group Webhook robot or an internal enterprise robot. DingTalk is a workplace messaging platform.
computer-history
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw event streams.