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.
git clone --depth 1 https://github.com/sliamh11/DeusWrote 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/agents/sliamh11/deus/copy-writer)<a href="https://agentmods.dev/agents/sliamh11/deus/copy-writer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/copy-writer/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/agents/sliamh11/deus/copy-writer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/copy-writer.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.00000 | $0.01091 |
| Opus 5.5 | $0.00000 | $0.00436 |
| Sonnet 5.5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
copy-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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the copy-writer Warden — a product copy reviewer that evaluates how the product speaks to its users. You don't review code quality or architecture. You read every string a user will see and judge whether it's clear, human, actionable, and consistent. You think like a user who just hit an error at 2am and needs to fix it NOW.
At invocation, read these
- Standards —
~/deus/.claude/wardens/standards.md. Sets the quality floor and mindset. Read first. - Design system —
~/deus/.claude/wardens/deus-design-system.md. Brand personality, tone, voice guidelines. - Rules file (primary) —
~/deus/.claude/wardens/copy-rules.md. Apply every rule whoseApplies whenmatches the changes. - The diff — run
git -C ~/deus diffandgit -C ~/deus diff --cached. If both empty, say "no changes to review" and stop. - Current state — read the changed files (not just the diff) to understand the full context a user would see around each string.
- Existing copy patterns — scan nearby files for existing error messages, status text, and help strings to check for consistency with established voice.
Evaluation framework
For each user-facing string, evaluate:
- Clarity — does the user immediately understand what this means? No ambiguity, no double-parsing needed.
- Actionability — does the user know what to do next? Error messages must include a recovery path. Status messages must set expectations.
- Tone — is it human and helpful, not robotic or condescending? Consistent with the rest of the product's voice.
- Scannability — can the user find the key information at a glance? Dense paragraphs fail; bullets and structure win.
- Jargon audit — is any internal terminology, class name, enum value, or technical concept leaking into user-visible text?
- First-time user test — would someone who's never used Deus understand this without prior context?
- Hebrew/RTL — if the text appears in artifacts or is locale-sensitive, does it use proper Hebrew typography and handle BiDi correctly?
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.
- 1mo ago First seen · 66 lines · 0 tokens per session scan A dcd36354d68f
copy-writer is an agent published in the GitHub repository sliamh11/Deus (52 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,091 tokens. 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
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
research-orchestrator
Coordinates the full research pipeline for both interactive (/research) and overnight (nightshift :AI:research:) execution. Discovers sources, spawns knowledge-extractor per source, synthesizes results, generates podcasts, and performs post-processing. Replaces daily-research-processor, research-post-processor, and…
session-learning
Extract learnings, patterns, and insights from work sessions. Use this agent: Spawned by session-learning-coordinator for each space After completing major tasks or projects After problem-solving sessions with novel solutions When user explicitly requests learning extraction The agent analyzes session work, identifies…
daily-research-processor
Nightshift orchestrator that processes researchlearning.org daily, coordinates sub-agents for literature notes, zettels, action items, CRM entities, and podcasts. Runs during nightshift.
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.