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 skills/dkstm95/hope/writenpx skills add dkstm95/hope --skill writegit clone --depth 1 https://github.com/dkstm95/hopeWhat 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.00049 | $0.00379 |
| Opus 5 | $0.00024 | $0.00189 |
| Sonnet 5 | $0.00010 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
write 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.
What it actually says
Hope Write
Use the active host session to draft, edit, review, or improve language. Read
references/writing-standard.md before doing the work.
Write may own a standalone language task or accompany another task or Skill. When it accompanies other work, preserve that work's scope, authority, process, and completion conditions. Apply the standard to its language-bearing parts in the same session; do not create a separate Write workflow, result, or worker.
Choose the language action
draftcreates new prose.editchanges existing prose or files.reviewreports material clarity, meaning, or flow problems without changing the target.
Infer the action when the request already makes it clear. It describes the language work, not the surrounding task: implementation, feature changes, architecture migrations, and broad restructuring remain ordinary work.
Return the requested result
For a draft, lead with the requested text and only its necessary context. For an edit, make the authorized change and report the result. For a review, report material findings without editing the target.
Use the current language unless the person or project chooses another. For translated or parallel text, first read the target version for naturalness, then compare versions for meaning drift.
Do not copy the writing standard or its checklist into the response.
Return when the requested language action is complete and meaning, facts, uncertainty, citations, exact text, and voice remain preserved. Correct a clarity or preservation problem introduced by Write, but do not continue polishing beyond the requested result.
What ships with it
3 files 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.
- 2d ago First seen · 43 lines · 49 tokens per session scan A c4e40365ecfb
write is a skill published in the GitHub repository dkstm95/hope (8 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 379 once invoked, about $0.0002 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-31.
Other skills, from other repositories
write-test-plan
Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).
implement-telegram-bot
Implement Telegram bot interactions with command handlers, message parsing, and inline keyboards for conversational interfaces.
write-unit-tests
Write comprehensive unit tests with proper setup, assertions, and coverage of happy paths, edge cases, and error scenarios.
integrate-graph-api
Integrate with Microsoft Graph API for email, calendar, and organizational data access with proper authentication and error handling.
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
blazor-component-design
Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.