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/huifer/wellally-health/fallgit clone --depth 1 https://github.com/huifer/WellAlly-healthWhat 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.00024 | $0.03147 |
| Opus 5 | $0.00012 | $0.01573 |
| Sonnet 5 | $0.00005 | $0.00629 |
| Haiku 4.5 | $0.00002 | $0.00315 |
Grade A, and why
fall 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 yesterday.
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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
跌倒风险评估命令 (Fall Risk Assessment)
功能概述
用于管理老年人跌倒风险评估，包括跌倒史记录、平衡功能测试、步态分析和居家环境安全评估。
⚠️ 安全红线
-
不处理跌倒后的损伤
- 跌倒受伤需立即就医
- 系统仅记录跌倒事件
-
不替代专业平衡功能评估
- 平衡测试需康复治疗师指导
- 系统记录测试结果
-
不给出具体康复训练处方
- 康复训练需专业评估
- 系统提供一般性建议
✅ 系统能做到的
- 跌倒风险因素评估
- 平衡功能测试记录(TUG/Berg/单腿站立)
- 步态分析记录
- 居家环境安全评估
- 跌倒预防建议
- 风险分级和干预建议
可用操作
1. 记录跌倒事件 - record
记录跌倒事件的详细信息。
参数说明:
info: 跌倒事件信息(必填)- 日期(YYYY-MM-DD格式)
- 地点(bathroom/bedroom/living_room/kitchen/stairs等)
- 原因(slippery_floor/trip/loss_balance/dizziness等)
- 损伤程度(none/bruise/cut/fracture/head_injury等)
执行步骤:
1. 参数识别
- 从info中提取日期、地点、原因、损伤
- 日期格式:
(\d{4}-\d{2}-\d{2}) - 地点关键词: bathroom, bedroom, living_room, kitchen, stairs
- 原因关键词: slippery, trip, dizzy, weak, sudden_movement
- 损伤关键词: bruise, cut, fracture, head_injury, none
2. 记录更新
- 更新
data/fall-risk-assessment.json - 更新
fall_history段 - 增加fall_count计数
- 标记last_fall信息
3. 风险重新评估
- 更新
previous_falls风险因素 - 重新计算overall_risk
4. 输出确认
- 显示跌倒事件摘要
- 显示跌倒次数统计
- 显示是否需要就医
示例:
/fall record 2025-03-15 bathroom slippery_floor bruise
/fall record 今天 卧室 地滑 轻微擦伤
2. 查看跌倒历史 - history
查看跌倒历史记录。
执行步骤:
1. 读取数据
- 读取
data/fall-risk-assessment.json - 提取
fall_history段
2. 显示历史报告
- 最近一次跌倒详情
- 过去一年跌倒次数
- 过去6个月跌倒次数
- 跌倒趋势
- 常见跌倒地点
- 常见跌倒原因
示例:
/fall history
3. TUG测试 - tug
记录Timed Up and Go测试结果。
参数说明:
info: TUG测试时间(秒)date: 测试日期(可选，默认今天)
结果解读:
- <10秒: 正常
- 10-19秒: 基本正常
- 20-29秒: 行动受限
- ≥30秒: 依赖他人
执行步骤:
1. 参数识别
- 从info中提取TUG时间
- 识别格式:
tug[:\s]+(\d+)或(\d+)\s*秒
2. 结果解读
- 根据时间判断行动能力
- 评估跌倒风险等级
3. 记录更新
- 更新
balance_tests.tug_test段 - 记录日期、时间、解读结果
4. 输出确认
- 显示TUG测试结果
- 显示行动能力评估
- 显示跌倒风险
示例:
/fall tug 18
/fall tug 22秒
4. Berg平衡量表 - berg
记录Berg平衡量表测试结果。
参数说明:
info: Berg量表总分(0-56分)date: 测试日期(可选，默认今天)
结果解读:
- 0-20分: 需坐轮椅
- 21-40分: 需辅助行走
- 41-56分: 独立行走
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.
- yesterday First seen · 451 lines · 24 tokens per session scan A 59605cb67c3c
fall is a command published in the GitHub repository huifer/WellAlly-health (935 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 3,147 once invoked, about $0.0001 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.