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/symptom.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/symptom)<a href="https://agentmods.dev/commands/huifer/wellally-health/symptom"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/symptom/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/symptom"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/symptom.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.00008 | $0.03298 |
| Opus 5 | $0.00004 | $0.01649 |
| Sonnet 5 | $0.00002 | $0.00660 |
| Haiku 4.5 | $0.00001 | $0.00330 |
Grade A, and why
symptom 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
身体不适感记录
记录日常身体不适和症状,自动转换为标准医学记录并提供就医建议。
操作类型
1. 记录症状 - add
记录身体不适感受,自动转换为结构化医学记录。
参数说明:
description: 症状描述(必填),用自然语言描述不适感受date: 症状发生日期(可选),格式 YYYY-MM-DD,默认为今天
示例:
/symptom add 头疼
/symptom add 胃疼 早上开始 2025-12-30
/symptom add 发烧38度 伴有咳嗽
/symptom add 胸闷气短 持续2小时
2. 查看历史 - history
查看所有症状记录。
示例:
/symptom history
/symptom history recent 10
3. 症状统计 - status
查看症状统计分析。
示例:
/symptom status
执行步骤
记录症状 (add)
1. 解析用户描述
从自然语言描述中提取以下信息:
基本信息(自动提取):
- 症状名称:标准医学术语
- 发生时间:具体时间点或时间段
- 持续时间:症状持续了多久
- 严重程度:轻度/中度/重度
- 身体部位:症状发生的具体位置
伴随症状(识别):
- 相关症状列表
- 全身症状(发热、乏力等)
诱因和缓解因素(提取):
- 诱发因素:运动、饮食、情绪、环境等
- 缓解因素:休息、用药、体位改变等
其他信息:
- 症状特点:性质、频率、进展等
- 既往史:是否曾出现类似症状
2. 医学标准化转换
将通俗描述转换为标准医学术语:
| 通俗描述 | 医学术语 |
|---|---|
| 头疼 | 头痛/头痛 |
| 胃疼 | 胃痛/上腹痛 |
| 心慌 | 心悸 |
| 气短 | 呼吸困难 |
| 拉肚子 | 腹泻 |
| 便秘 | 便秘 |
| 恶心 | 恶心 |
| 吐 | 呕吐 |
| 头晕 | 头晕/眩晕 |
3. 症状分类
按系统分类:
- 呼吸系统:咳嗽、咳痰、呼吸困难、胸痛等
- 心血管系统:心悸、胸闷、水肿等
- 消化系统:腹痛、恶心、呕吐、腹泻、便秘等
- 神经系统:头痛、头晕、失眠、抽搐等
- 泌尿系统:尿频、尿急、尿痛、血尿等
- 内分泌系统:多饮、多尿、体重变化等
- 肌肉骨骼:关节痛、肌肉痛、活动受限等
- 全身症状:发热、乏力、消瘦等
4. 严重程度评估
轻度(1级):
- 症状轻微,不影响日常活动
- 无需立即处理
- 可自行观察
中度(2级):
- 症状明显,部分影响日常活动
- 需要休息或简单处理
- 建议观察或门诊就医
重度(3级):
- 症状严重,严重影响日常活动
- 需要立即处理
- 建议尽快就医
危急(4级):
- 危及生命的症状
- 需要紧急就医
- 建议立即就医或拨打急救电话
5. 就医建议评估
立即就医(拨打120或急救):
- 胸痛或胸闷,特别是伴有出汗、呼吸困难
- 突然严重头痛
- 呼吸困难或窒息感
- 意识模糊或昏厥
- 严重外伤或大出血
- 急性腹痛(特别是老年人)
- 突然无法说话或肢体无力
尽快就医(今天或明天):
- 持续高烧超过3天
- 严重呕吐或腹泻导致脱水
- 持续加重的疼痛
- 无法解释的体重下降
- 持续的疲劳或虚弱
- 黄疸(皮肤或眼睛发黄)
门诊就医(1周内):
- 轻中度症状持续超过1周
- 反复出现的症状
- 需要进一步检查的症状
居家观察:
- 轻度症状,时间短
- 症状逐渐好转
- 无加重趋势
6. 保存记录
文件路径格式:
data/症状记录/YYYY-MM/YYYY-MM-DD_主要症状.json
JSON 数据结构:
{
"id": "20251231123456789",
"record_date": "2025-12-31",
"symptom_date": "2025-12-31",
"original_input": "用户原始输入",
"standardized": {
"main_symptom": "头痛",
"category": "神经系统",
"body_part": "头部",
"severity": "轻度",
"severity_level": 1,
"characteristics": "胀痛感",
"onset_time": "2025-12-31T10:00:00",
"duration": "2小时",
"frequency": "首次出现"
},
"associated_symptoms": [
{
"name": "恶心",
"present": true
},
{
"name": "呕吐",
"present": false
}
],
"triggers": {
"possible_causes": ["睡眠不足", "精神紧张"],
"aggravating_factors": [],
"relieving_factors": ["休息后略缓解"]
},
"medical_assessment": {
"urgency": "observation",
"urgency_level": 1,
"recommendation": "居家观察",
"advice": "建议充分休息,保证充足睡眠。如症状加重或持续超过24小时,建议就医。",
"red_flags": []
},
"follow_up": {
"needs_follow_up": false,
"follow_up_date": null,
"improvement": null
},
"metadata": {
"created_at": "2025-12-31T12:34:56.789Z",
"last_updated": "2025-12-31T12:34:56.789Z"
}
}
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 · 433 lines · 8 tokens per session scan A 7ead903e4867
symptom is a command published in the GitHub repository huifer/WellAlly-health (947 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 3,298 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.