Borrowing it
Nothing to install: this file belongs to huifer/WellAlly-health. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huifer/WellAlly-health/main/.claude/commands/menopause.mdgit clone --depth 1 https://github.com/huifer/WellAlly-healthWrote 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/huifer/wellally-health/menopause)<a href="https://agentmods.dev/commands/huifer/wellally-health/menopause"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/menopause/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/huifer/wellally-health/menopause"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/menopause.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.09714 |
| Opus 5 | $0.00005 | $0.04857 |
| Sonnet 5 | $0.00002 | $0.01943 |
| Haiku 4.5 | $0.00001 | $0.00971 |
Grade A, and why
menopause 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 — 1,350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
更年期管理
围绝经期症状追踪和管理,提供更年期健康评估和管理建议。
操作类型
1. 开始更年期追踪 - start
初始化更年期追踪记录。
参数说明:
info: 更年期基本信息(必填)- 年龄:数字
- 末次月经日期:YYYY-MM-DD
示例:
/menopause start 48 2025-11-15
/menopause start age 48 last period November 15 2025
/menopause start 50岁 2025-06-01
执行步骤:
1. 解析输入信息
从自然语言中提取:
- 年龄:数字
- 末次月经日期 (LMP):精确日期
2. 验证输入
检查项:
- 年龄应在40-65岁之间
- LMP不能是未来日期
- LMP应在过去12个月内
3. 确定更年期阶段
更年期阶段定义:
| 阶段 | 定义 | 月经模式 | 时间范围 |
|---|---|---|---|
| 围绝经期 | Perimenopausal | 周期不规律 | 40-55岁 |
| 绝经 | Menopausal | 停经12个月 | LMP + 12个月 |
| 绝经后 | Postmenopausal | 停经>12个月 | >12个月 |
判断逻辑:
months_since_lmp = (today - lmp_date) / 30.44
if (months_since_lmp < 12) {
stage = "perimenopausal" // 围绝经期
} else if (months_since_lmp >= 12 && months_since_lmp < 36) {
stage = "menopausal" // 绝经
} else {
stage = "postmenopausal" // 绝经后
}
4. 创建更年期记录
生成 menopause_id:menopause_YYYYMMDD
更年期数据结构:
{
"menopause_id": "menopause_20250101",
"stage": "perimenopausal",
"age": 48,
"last_menstrual_period": "2025-11-15",
"months_since_lmp": 0,
"symptoms": {
"hot_flashes": {
"present": false,
"frequency": null,
"severity": null,
"impact_on_life": null,
"triggers": [],
"last_updated": null
},
"night_sweats": {
"present": false,
"frequency": null,
"severity": null
},
"sleep_issues": {
"present": false,
"type": null,
"sleep_quality": null
},
"mood_changes": {
"present": false,
"symptoms": []
},
"vaginal_dryness": {
"present": false,
"severity": null
},
"joint_pain": {
"present": false,
"severity": null,
"locations": []
}
},
"symptom_history": [],
"hrt": {
"on_treatment": false,
"considering": false,
"medication": null,
"type": null,
"dose": null,
"route": null,
"start_date": null,
"duration": null,
"effectiveness": null,
"effectiveness_rating": null,
"side_effects": [],
"notes": ""
},
"bone_density": {
"last_check": null,
"t_score": null,
"z_score": null,
"diagnosis": null,
"diagnosis_category": null,
"fracture_risk": null,
"fracture_risk_level": null,
"next_check_due": null,
"calcium_intake": {},
"vitamin_d": {},
"weight_bearing_exercise": null,
"fall_risk_factors": []
},
"cardiovascular_risk": {
"last_assessment": null,
"blood_pressure": null,
"systolic": null,
"diastolic": null,
"bp_classification": null,
"lipids": {},
"blood_sugar": {},
"risk_level": null,
"risk_factors": [],
"modifiable_factors": []
},
"lifestyle": {
"exercise": {},
"diet": {},
"stress_management": [],
"sleep_habits": null
},
"metadata": {
"created_at": "2025-01-01T00:00:00.000Z",
"last_updated": "2025-01-01T00:00:00.000Z"
}
}
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 · 1,350 lines · 9 tokens per session scan A e7a4dc7d8c54
menopause is a command published in the GitHub repository huifer/WellAlly-health (943 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 9,714 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
health
Run health checks on the Claude orchestration system.
health
Scan all projects for stale research, forgotten ADRs, unresolved review conditions, orphaned artifacts, missing traceability, and version drift.
roster-doctor
Health check and dev-environment pre-flight for the roster install and its build/test/lint tooling.
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.