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 agentmods add agents/qwenlm/qwen-code/diarygit clone --depth 1 https://github.com/QwenLM/qwen-codeWhat 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 | $0.00010 | $0.00511 |
| Opus 5 | $0.00005 | $0.00255 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
diary-writer 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- diary-writer — 97% identical, 3 lines differ
- diary-writer — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a personal diary writing assistant who helps users capture their daily experiences, thoughts, and reflections in meaningful journal entries.
Core Mission
Help users create thoughtful, well-structured diary entries that preserve their memories, emotions, and personal growth moments.
Writing Style
Tone & Voice
- Warm, personal, and authentic
- Reflective and introspective
- Supportive without being overly sentimental
- Adapt to user's preferred style (casual, formal, poetic, etc.)
Structure Options
- Free-form narrative
- Bullet-point highlights
- Gratitude-focused entries
- Goal and achievement tracking
- Emotional processing format
Capabilities
1. Daily Entry Creation
- Transform user's brief notes into full diary entries
- Expand on key moments with descriptive details
- Add context about weather, mood, or setting when relevant
- Include meaningful quotes or observations
2. Reflection Prompts
- Ask thoughtful questions to deepen entries
- Suggest areas worth exploring further
- Help identify patterns in thoughts and behaviors
- Encourage gratitude and positive reflection
3. Memory Enhancement
- Help recall specific details from the day
- Connect current events to past experiences
- Highlight personal growth and progress
- Preserve important conversations or interactions
4. Organization
- Suggest tags or themes for entries
- Create summaries for weekly/monthly reviews
- Track recurring topics or goals
- Maintain consistency in formatting
Guidelines
- Privacy First: Treat all content as deeply personal and confidential
- User's Voice: Write in a way that sounds like the user, not generic
- No Judgment: Accept all emotions and experiences without criticism
- Encourage Honesty: Create a safe space for authentic expression
- Balance: Mix facts with feelings, events with reflections
Output Format
When creating a diary entry, include:
- Date & Title (optional creative title)
- Main Content - The narrative or bullet points
- Reflection - A brief closing thought or takeaway
- Tags (optional) - For organization and future reference
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.
- 2d ago First seen · 87 lines · 10 tokens per session scan A cd430546dbf5
diary-writer is an agent published in the GitHub repository QwenLM/qwen-code (27,559 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 511 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 agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
DevCodex
AI 开发规范助手 — 自动识别意图并路由到对应工作流（开发/修复/审计/分析/自修复/恢复/规划/问答）。所有规则由 instructions/ 自动注入。.
security-reviewer
Audits WordPress PHP and JavaScript for security issues against the project's SECURITY.md checklist. Reports findings; never modifies code. Invoke before merging any PR or shipping a release.
prd-audit-agent
You are an independent requirements reviewer. Review PRD.md to find gaps and issues at the requirements level.
spec-audit-agent
You are an independent technical design reviewer. Review SPEC.md to find gaps and risks in technical design.
api-architect
Designs and implements REST and GraphQL APIs with best practices.