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 agentmods add commands/womendefiningai/claudecode-writer/researchgit clone --depth 1 https://github.com/WomenDefiningAI/claudecode-writerWrote 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/womendefiningai/claudecode-writer/research)<a href="https://agentmods.dev/commands/womendefiningai/claudecode-writer/research"><img src="https://agentmods.dev/badge/commands/womendefiningai/claudecode-writer/research.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 | $0.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
research 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 5d 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
Research Command
Use this command to develop and refine content ideas before writing.
Usage
/research [topic]
What This Command Does
- Explores the topic from multiple angles
- Identifies key insights and unique perspectives
- Suggests compelling hooks and storylines
- Researches supporting data and examples
- Outlines potential article structure
Process
- Priority Source Check: Start with sources in @context/research-sources.md - check these FIRST
- Gap Analysis: Identify what perspectives are missing from trusted source coverage
- Trend Investigation: Check Google Trends, industry reports, social media discussions
- Counter-narrative Search: Look for contrarian views or unexplored angles
- Data Mining: Find recent studies, surveys, or statistics to support points
- Expert Voices: Identify who else is talking about this and what they're missing
- Audience Pulse: Research what questions people are actually asking about this topic
- Broader Web Search: Expand beyond priority sources for comprehensive coverage
Output
Provides a research brief with:
- Trend Context: What's currently happening in this space
- Unique Angle: Your differentiated perspective vs. existing content
- Core Thesis: Main argument supported by fresh data/insights
- Supporting Evidence: Recent examples, studies, expert quotes
- Audience Questions: What people are actually asking about this topic
- Platform Hooks: Compelling angles for each repurposing agent
- Contrarian Elements: Unexpected or challenging viewpoints to explore
File Management
After completing the research, automatically save the brief to:
- File Location:
research/research-brief-[topic-slug]-[YYYY-MM-DD].md - File Format: Markdown with clear sections and headers
- Naming Convention: Use lowercase, hyphenated topic slug and current date
Example: research/research-brief-remote-work-productivity-2024-01-15.md
This ensures all research briefs are systematically stored and easily referenced for future writing projects.
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.
- 5d ago First seen · 43 lines · 0 tokens per session scan A 316bacde0ccc
research is a command published in the GitHub repository WomenDefiningAI/claudecode-writer (221 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 445 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.