Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jamditis/claude-skills-journalism/plugin install pdf-playgroundWrote 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/commands/jamditis/claude-skills-journalism/newsletter)<a href="https://agentmods.dev/commands/jamditis/claude-skills-journalism/newsletter"><img src="https://agentmods.dev/badge/commands/jamditis/claude-skills-journalism/newsletter/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/commands/jamditis/claude-skills-journalism/newsletter"><img src="https://agentmods.dev/badge/commands/jamditis/claude-skills-journalism/newsletter.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.00009 | $0.00379 |
| Opus 5 | $0.00005 | $0.00189 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
newsletter 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 12d 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
Create an HTML email newsletter.
Version check
Read the plugin version from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json and note it. If the file doesn't exist or the read fails, warn the user that the plugin may not be properly installed.
Setup
- Check for brand configuration at
.claude/pdf-playground.local.md - If found, parse the YAML frontmatter for brand settings
- Load the newsletter template from
${CLAUDE_PLUGIN_ROOT}/templates/newsletter-template.html
Email constraints
HTML emails have special requirements:
- Use tables for layout (not CSS grid/flexbox)
- Inline CSS styles
- Max width: 600px
- Web-safe fonts with fallbacks
- Alt text for all images
Document structure
Header:
- Organization logo centered
- Newsletter title/date
- View in browser link (placeholder)
Content:
- Featured story with image placeholder
- News items (headline + excerpt + link)
- Upcoming events
- Quick links
- CTA button
Footer:
- Social media links
- Unsubscribe link (placeholder)
- Organization address
- Copyright
Brand application
- Use brand primary color for headers and buttons
- Apply brand secondary color for text
- Use brand fonts with web-safe fallbacks
Newsletter name
The newsletter name is: $ARGUMENTS
If not provided, ask for:
- Newsletter title or edition
- Featured content
- Number of news items
- Any events to highlight
Output
Save HTML file in current working directory. Note: Test in email clients before sending.
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.
- 12d ago First seen · 68 lines · 9 tokens per session scan A 2f4b54875665
newsletter is a command published in the GitHub repository jamditis/claude-skills-journalism (391 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 379 once invoked, about $0.0000 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-30.
Other commands, from other repositories
export-latex
Export the current paper draft to production-ready LaTeX (.tex) and PDF using the arxiv-style template. Converts draft.md + references.bib + figures/ into a complete LaTeX project with resolved citations, tables, and figures. Compiles to PDF automatically.
review-paper
Simulate a double-blind peer review of the current paper. Generates 2 independent reviewer reports in the style of top IS/CS conferences (ICIS, ECIS, MISQ level). Each report includes Summary, Strengths, Weaknesses, Minor Comments, and Overall Recommendation. Output is saved as simulatedreviews.md and can be fed…
triage-project
Strategic project triage — should you continue, pivot, or kill your current research project? Evaluates 5 signals (results, competition, impact, effort, motivation) and delivers a clear Continue/Pivot/Kill recommendation. For Pivot: suggests concrete new framing. For Kill: suggests what to salvage.
analyze-writing
Analyze academic writing quality of the current draft. Checks for passive voice overuse, weak openings, hedging balance, readability, sentence length variation, and word repetitions. Produces a writing quality report with specific improvement suggestions per section.
scooping-check
Scooping risk assessment — is someone else working on your research idea? Identifies competing groups, assesses pace of publication, evaluates whether the core insight is "in the air", and provides a watch list with search terms, key researchers, and venues to monitor.
audit-paper
Audit a paper's empirical claims against the linked code repository — catches MISMATCH, MISSING, and PARTIAL claims before submission.