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/male-fertility.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/male-fertility)<a href="https://agentmods.dev/commands/huifer/wellally-health/male-fertility"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/male-fertility/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/male-fertility"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/male-fertility.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.07120 |
| Opus 5 | $0.00005 | $0.03560 |
| Sonnet 5 | $0.00002 | $0.01424 |
| Haiku 4.5 | $0.00001 | $0.00712 |
Grade A, and why
male-fertility 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 13d 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,088 lines — stays where its author put it; the contents beside it link to each section on GitHub.
男性不育管理
男性生育健康追踪和管理,包括精液分析记录、激素水平监测、不育因素评估。
操作类型
1. 记录精液分析 - semen
记录精液分析结果,WHO 2021标准。
参数说明:
info: 精液分析信息(必填)- 参数类型: volume(精液量)/concentration(密度)/motility(活力)/morphology(形态)/ph(pH)/liquefaction(液化)
- 数值: 根据参数类型提供相应数值
- 精子活力: pr(前向运动), np(非前向运动)
示例:
/fertility semen volume 2.5
/fertility semen concentration 45
/fertility semen motility pr 35 np 20
/fertility semen morphology 4
/fertility semen ph 7.5
/fertility semen complete # 完整记录
执行步骤:
1. 精液分析标准(WHO 2021)
精液量:
- 正常: ≥ 1.5 mL
- 异常: < 1.5 mL(精液减少)
- 无精: 0 mL
精子密度:
- 正常: ≥ 15 × 10⁶/mL
- 少精症: < 15 × 10⁶/mL
- 无精症: 0 × 10⁶/mL
精子总数:
- 正常: ≥ 39 × 10⁶/每次射精
精子活力:
- PR(前向运动,progressive): ≥ 32%
- NP(非前向运动,non-progressive): ≥ 40%
- 弱精症: PR < 32%
精子形态:
- 正常形态率: ≥ 4%
- 畸形精子症: < 4%
精液pH值:
- 正常: 7.2-8.0
- 异常: < 7.2 或 > 8.0
液化时间:
- 正常: ≤ 60分钟
2. 解析精液分析信息
参数识别:
// 精液量
volume_patterns = [
/volume[:\s]+(\d+\.?\d*)/i,
/精液量[:\s]+(\d+\.?\d*)/i,
/(\d+\.?\d*)\s*ml/i
]
// 精子密度
concentration_patterns = [
/concentration[:\s]+(\d+)/i,
/密度[:\s]+(\d+)/i,
/(\d+)\s*10.*6.*ml/i
]
// 活力
motility_patterns = [
/pr[:\s]+(\d+)/i,
/前向运动[:\s]+(\d+)/i,
/np[:\s]+(\d+)/i
]
// 形态
morphology_patterns = [
/morphology[:\s]+(\d+)/i,
/形态[:\s]+(\d+)/i
]
3. 诊断评估
精液分析结果分类:
| 结果 | 诊断 |
|---|---|
| 所有参数正常 | 正常精液(normospermia) |
| 精子密度<15 | 少精症(oligozoospermia) |
| 精子密度=0 | 无精症(azoospermia) |
| PR<32% | 弱精症(asthenozoospermia) |
| 正常形态<4% | 畸形精子症(teratozoospermia) |
| 精液量<1.5mL | 精液减少(hypospermia) |
| 多个异常 | 混合异常 |
4. 更新精液分析记录
精液分析数据结构:
{
"semen_analysis": {
"date": "2025-06-20",
"abstinence_period": "3_days",
"volume": {
"value": 2.5,
"unit": "mL",
"reference": "≥1.5",
"result": "normal"
},
"concentration": {
"value": 45,
"unit": "10⁶/mL",
"reference": "≥15",
"result": "normal"
},
"total_count": {
"value": 112.5,
"unit": "10⁶",
"reference": "≥39",
"result": "normal"
},
"motility": {
"pr": {
"value": 35,
"reference": "≥32",
"result": "normal"
},
"np": {
"value": 20,
"reference": "≥40",
"result": "normal"
},
"im": {
"value": 45,
"result": "normal"
}
},
"morphology": {
"value": 4,
"unit": "%",
"reference": "≥4",
"result": "normal"
},
"ph": {
"value": 7.5,
"reference": "7.2-8.0",
"result": "normal"
},
"liquefaction": {
"value": 30,
"unit": "minutes",
"reference": "≤60",
"result": "normal"
},
"diagnosis": "normospermia"
}
}
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.
- 13d ago First seen · 1,088 lines · 9 tokens per session scan A 45b0e8698be2
male-fertility is a command published in the GitHub repository huifer/WellAlly-health (948 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 7,120 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.