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/jamditis/claude-skills-journalismWrote 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/setup)<a href="https://agentmods.dev/commands/jamditis/claude-skills-journalism/setup"><img src="https://agentmods.dev/badge/commands/jamditis/claude-skills-journalism/setup.svg" alt="Measured on agentmods" 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.02689 |
| Opus 5 | $0.00005 | $0.01345 |
| Sonnet 5 | $0.00002 | $0.00538 |
| Haiku 4.5 | $0.00001 | $0.00269 |
Grade A, and why
setup 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 7d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the autocontext first-run setup wizard. Use AskUserQuestion for each step. Group questions into batches of 2 (up to 4 per AskUserQuestion call) to keep the flow efficient.
Setup workflow
This skill guides you through initial configuration of the autocontext plugin. Your answers will be saved to ~/.claude/autocontext.json for use across all projects.
If ~/.claude/autocontext.json already exists, read it first and present current values as defaults. The user is re-running setup to change settings.
Batch 1 (steps 1-2)
Step 1: Identity
Identity is required for lesson attribution. No automatic fallback, you must explicitly set it.
Question: What should we call you in lesson attribution?
Options:
- Your name (text input)
- Username (text input)
- Email address (text input)
- Other (text input)
Step 2: Test quality rules
Select which automated test quality checks you want enabled when reviewing test code.
Question: Which built-in test quality rules do you want enabled?
Available rules (multi-select):
- Tautological test check, flags tests that describe code instead of testing behavior
- No mock everything, warns when mocks are the assertions instead of testing actual behavior
- No happy path only, requires error cases and edge case tests alongside happy path
- No bare assertions, flags
assert True,assert is not None, and similar weak assertions - Test independence, flags tests that pass without their feature code present
You can enable all, some, or none of these. They can be toggled later.
Batch 2 (steps 3-4)
Step 3: Lesson loading aggressiveness
Configure how many lessons to load at session start based on relevance confidence.
Question: How aggressively should lessons be loaded at session start?
Options:
- Conservative, load up to 5 lessons with confidence >= 0.7. Minimal context, high precision.
- Balanced (Recommended), load up to 15 lessons with confidence >= 0.3. Good mix of depth and specificity.
- Aggressive, load up to 25 lessons with confidence >= 0.1. Maximum context, may include tangential material.
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.
- 7d ago First seen · 267 lines · 9 tokens per session scan A edbca1bc2786
setup is a command published in the GitHub repository jamditis/claude-skills-journalism (386 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 2,689 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…
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.
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.
audit-paper
Audit a paper's empirical claims against the linked code repository — catches MISMATCH, MISSING, and PARTIAL claims before submission.