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 skills/saolalab/clawforce/user-researchnpx skills add saolalab/clawforce --skill user-researchgit clone --depth 1 https://github.com/saolalab/clawforceWhat 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.00036 | $0.01054 |
| Opus 5 | $0.00018 | $0.00527 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
user-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 3d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Research
User Interview Question Templates
Discovery Interview (Problem Discovery)
- What problem are you trying to solve?
- How do you currently solve this problem?
- What's frustrating about your current solution?
- What would make your life easier?
- Walk me through a typical day when you encounter this problem.
Feature Validation Interview
- How would you use this feature?
- What would make you want to use this?
- What concerns do you have?
- What's missing from this solution?
- Would you pay for this? How much?
Post-Launch Interview
- Have you tried [feature]? What was your experience?
- What worked well? What didn't?
- What would make you use it more?
- Would you recommend it to others? Why or why not?
Survey Design Guidelines
Good Survey Questions
- Start broad, narrow down — General questions first, specific later
- Use closed-ended for quantitative — "On a scale of 1-5..."
- Use open-ended for qualitative — "Tell me about..."
- Avoid leading questions — "Don't you think X is great?" → "How do you feel about X?"
- Keep it short — 5-10 questions max for high completion rates
Survey Template
# Survey: {Topic}
1. How often do you {relevant action}? (Daily / Weekly / Monthly / Rarely / Never)
2. What's your biggest challenge with {topic}? (Open-ended)
3. How satisfied are you with {current solution}? (1-5 scale)
4. What feature would most improve your experience? (Multiple choice)
5. Any additional feedback? (Open-ended)
Persona Template
# Persona: {Persona Name}
## Demographics
- **Role**: {Job title/role}
- **Age**: {Range}
- **Location**: {Geographic context}
- **Company Size**: {If B2B}
## Goals
- {Primary goal 1}
- {Primary goal 2}
- {Primary goal 3}
## Pain Points
- {Pain point 1}
- {Pain point 2}
- {Pain point 3}
## Behaviors
- {How they currently solve problems}
- {Tools they use}
- {How they make decisions}
## Quote
"{Representative quote that captures their perspective}"
## How We Help
{How our product addresses their goals and pain points}
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.
- 3d ago First seen · 156 lines · 36 tokens per session scan A 12b0f14ae992
user-research is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,054 once invoked, about $0.0002 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 skills, from other repositories
agenticmail
🎀 AgenticMail — Full email, SMS, storage & multi-agent coordination for AI agents. 63 tools.
ai-meeting-scheduling
Booking links fail for groups. SkipUp schedules meetings with 2-50 participants via email — one API call coordinates across timezones automatically. Also: check status, pause, resume, or cancel requests. Async only — does not instant-book, access calendars, or do free/busy lookups.
agentic-paper-digest-skill
Fetches and summarizes recent arXiv and Hugging Face papers with Agentic Paper Digest. Use when the user wants a paper digest, a JSON feed of recent papers, or to run the arXiv/HF pipeline.
eachlabs-voice-audio
Text-to-speech, speech-to-text, voice conversion, and audio processing using EachLabs AI models. Supports ElevenLabs TTS, Whisper transcription with diarization, and RVC voice conversion. Use when the user needs TTS, transcription, or voice conversion.
arxiv-summarizer-orchestrator
End-to-end orchestration skill for periodic arXiv collection and reporting using three sub-skills: arxiv-search-collector, arxiv-paper-processor, and arxiv-batch-reporter. Supports manual language control across all markdown outputs and Stage-B processing strategy (subagentparallel default max 5, or serial).
academic-literature-search
这是一个专注于学术文献检索的专业工具，集成了多个权威学术数据库，提供全面、快速、准确的文献检索服务。支持多数据库并发检索、高级过滤、智能排序和多种输出格式。.