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 mostafa-drz/claude-skills --skill enrich-messagegit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/enrich-message)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/enrich-message"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/enrich-message/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/mostafa-drz/claude-skills/enrich-message"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/enrich-message.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.02123 |
| Opus 5 | $0.00000 | $0.01061 |
| Sonnet 5 | $0.00000 | $0.00425 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
enrich-message 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 11d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enrich Message
Enrich a draft message with code references, ticket links, and factual data. Outputs copy-pasteable markdown.
Preferences
Before starting, use the Read tool to read ~/.claude/skills/enrich-message/preferences.md. If the file does not exist, treat as "no preferences set" and use defaults.
Context
On startup, use Bash to detect: current git branch, remotes, repo root, and recent commits (last 5). Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete preferences, confirm, stop- anything else (including empty) → run the skill
Help
Enrich Message — Enriches draft messages with code references, tickets, and facts
Usage:
/enrich-message Enrich draft from conversation context
/enrich-message <url> Enrich with a specific thread URL pre-loaded
/enrich-message --brief Keep enrichment concise
/enrich-message --no-linear Skip Linear ticket search
/enrich-message config Set preferences
/enrich-message reset Clear preferences
/enrich-message help This help
Examples:
/enrich-message Paste your draft + context in chat, then run
/enrich-message https://github.com/org/repo/pull/123#discussion_r456
Pre-fetch this PR discussion thread
Current preferences:
(from preferences.md or defaults)
Config
Use AskUserQuestion to collect:
- Q1: Default GitHub org — e.g.,
A-Teams-Network(used to resolve short PR refs) - Q2: Writing style — Professional / Casual / Match original tone
- Q3: Reference depth — Minimal (links only) / Standard (links + brief context) / Deep (links + code snippets + explanation)
Save to ~/.claude/skills/enrich-message/preferences.md.
Reset
Delete ~/.claude/skills/enrich-message/preferences.md and confirm: "Preferences cleared. Using defaults."
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.
- 11d ago First seen · 206 lines · 0 tokens per session scan A 735b1e4245df
enrich-message is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,123 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-31.
Other skills, from other repositories
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
ensemble-solving
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
code-execution
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
feature-planning
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.