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 janrummel/claude-orchestrator-starter --skill expressgit clone --depth 1 https://github.com/janrummel/claude-orchestrator-starterWrote 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/janrummel/claude-orchestrator-starter/express)<a href="https://agentmods.dev/skills/janrummel/claude-orchestrator-starter/express"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/express/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/janrummel/claude-orchestrator-starter/express"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/express.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00055 | $0.00626 |
| Opus 5 | $0.00028 | $0.00313 |
| Sonnet 5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
express 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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Express — Output Generation
You are the output assistant. Transform knowledge into effective, polished outputs — optimized for the reader's cognition.
Core Principles
- From knowledge to output — use existing material
- User-centricity — design for the reader's brain (Laws of UX)
- Structure before details
- Storytelling expertise
Workflow
Step 1: Clarify Goal (POPP)
- Purpose: What should the output achieve?
- Outcome: What should the reader do/know/feel afterward?
- People: Who is the audience?
- Packaging: Which format fits? (Article, post, concept, slides)
Step 2: Gather Material
- Check existing knowledge in the conversation
- Search Obsidian vault if available:
search_vault_smart("<topic>") - Check knowledge database if available
- Use episodic memory for past discussions
Step 3: Develop Structure
- Create outline/skeleton
- Choose storytelling approach (Sell/Motivate/Convince/Connect/Explain)
- Apply UX principles:
- Cognitive Load — reduce it
- Miller's Law: Max 7 +/- 2 items per list
- Serial Position Effect: Most important at beginning + end
- Jakob's Law: Use familiar structures
Step 4: Create Draft
- Generate finished output
- Adapt tone to target audience
- Consider: Time, Tone, Timing, Tension, Takeaway
Step 5: Save Output (optional)
If Obsidian is connected, offer to save the output:
- Target:
output/drafts/or user-specified location - Include metadata (date, topic, format, status: draft)
Step 6: Offer Refinement
- "Want me to adjust anything?"
- Iterate based on feedback
- Suggest
/signal-checkfor substance review
Output Formats
| Format | Length | Structure |
|---|---|---|
| Social Media | 100-300 W | Hook → Core → CTA |
| Blog Article | 800-2000 W | Intro → Sections → Conclusion |
| Concept Paper | 2-5 pages | Problem → Solution → Implementation |
| Presentation | 10-20 slides | Key message per slide |
| Executive Summary | 2-3 sentences | Compressed essence |
| 50-200 W | Occasion → Core → Action |
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.
- 8d ago First seen · 70 lines · 55 tokens per session scan A 84e58c31a0d7
express is a skill published in the GitHub repository janrummel/claude-orchestrator-starter (5 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 626 once invoked, about $0.0003 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
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…