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/alignnpx skills add dkstm95/hope --skill aligngit 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.00025 | $0.00940 |
| Opus 5 | $0.00013 | $0.00470 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
align 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hope Align
Inspect the task and interview the person until every material intent decision is explicit and shared. Align does not implement the task.
Do not start or manage a host goal, implementation loop, retry state, progress, or completion evidence.
Read ../write/references/writing-standard.md before drafting user-facing
language. Apply it without changing the agreement, evidence distinctions,
confirmation conditions, or artifact contract.
Inspect the task
Read available repository, document, and conversation evidence before asking a question. Facts belong to the evidence; intent decisions belong to the person. Do not ask the person to repeat a fact that the evidence can answer.
Keep facts, user decisions, AI proposals, assumptions, material questions, and research or implementation uncertainty distinct.
Test whether the requested work is likely to achieve the goal. Surface only an omission, contradiction, risk, unsupported assumption, edge case, or materially simpler path that could change the intended result or prevent material harm. For each concern, explain the issue, impact, evidence, and uncertainty. Do not invent concerns, treat taste as a defect, or widen the task because another product could be better.
If the person supplies an Align artifact path, read references/artifact.md
and inspect it as evidence. Do not search for a repository-wide latest artifact.
Work the intent tree
Map the task as an intent tree. A branch is material when different answers could change any of these:
- the observable outcome;
- deliberately excluded work;
- a person-visible or domain-visible flow;
- who can judge the result; or
- the risk of material harm.
The frontier is every unresolved material decision whose prerequisites are settled. Ask the whole frontier in one round. Number the questions, explain why each answer matters, and offer realistic options with a recommended default when one is sensible. Do not ask a dependent question in the same round as its prerequisite.
What ships with it
9 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.
- agents/openai.yaml 265 B
- references/artifact.md 6.7 KB
- references/design-directions.md 3.7 KB
- scripts/align-input-v3.schema.json 7.5 KB
- scripts/artifact.mjs 47 KB runs code
- scripts/cli.mjs 3.6 KB runs code
- scripts/design/tokens.mjs 2.0 KB runs code
- scripts/image.mjs 6.3 KB runs code
- scripts/render.mjs 68 KB runs code
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 · 120 lines · 25 tokens per session scan A 45f73b749a65
align is a skill published in the GitHub repository dkstm95/hope (8 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 940 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-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.
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
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.
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.