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/vaccine.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/vaccine)<a href="https://agentmods.dev/commands/huifer/wellally-health/vaccine"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/vaccine/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/vaccine"><img src="https://agentmods.dev/badge/commands/huifer/wellally-health/vaccine.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.08336 |
| Opus 5 | $0.00004 | $0.04168 |
| Sonnet 5 | $0.00002 | $0.01667 |
| Haiku 4.5 | $0.00001 | $0.00834 |
Grade A, and why
vaccine 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 12d 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,170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
疫苗接种管理
管理疫苗接种记录和计划,支持多剂次疫苗追踪、接种计划管理、不良反应记录和安全检查。
操作类型
1. 添加疫苗接种计划 - add
添加新的疫苗接种计划或记录已接种疫苗。
参数说明:
info: 疫苗信息(必填),使用自然语言描述date: 接种日期(可选),格式:YYYY-MM-DD,默认今天
示例:
/vaccine add 乙肝疫苗 0-1-6程序 第一针已打昨天
/vaccine add HPV疫苗 第一针2025-10-15 第二针计划2025-12-15
/vaccine add 流感疫苗 2025-10-01已接种
/vaccine add COVID-19疫苗 第一剂今天接种
支持的描述格式:
- 疫苗名称 + 接种程序(0-1-6、2-6等)
- 已接种信息(第几针、接种日期、部位、接种单位)
- 计划信息(后续剂次的计划日期)
- 详细信息(厂家、批号、医生等)
2. 记录疫苗接种 - record
记录实际疫苗接种情况。
参数说明:
info: 接种信息(必填),使用自然语言描述date: 接种日期(可选),格式:YYYY-MM-DD,默认今天
示例:
/vaccine record 乙肝疫苗 第2针 今天左上臂
/vaccine record 流感疫苗 今天社区卫生服务中心
/vaccine record HPV第2针 2025-12-15 右上臂 李医生
支持的描述格式:
- 疫苗名称 + 剂次 + 日期 + 接种部位
- 疫苗名称 + 日期 + 接种单位
- 疫苗名称 + 剂次 + 详细信息
3. 查看接种计划 - schedule
查看疫苗接种计划和即将接种的疫苗。
示例:
/vaccine schedule
/vaccine schedule 2025-12
/vaccine schedule 2026-01
4. 查看待接种疫苗 - due
快速查看待接种和逾期的疫苗。
示例:
/vaccine due
/vaccine due overdue
/vaccine due upcoming
5. 查看接种历史 - history
查看疫苗接种历史记录。
参数说明:
- 无参数:显示全部历史
date: 月份(YYYY-MM格式)
示例:
/vaccine history
/vaccine history 2025-10
/vaccine history 2025-12
6. 查看接种统计 - status
查看疫苗接种统计和覆盖率。
示例:
/vaccine status
/vaccine status coverage
7. 接种前安全检查 - check
在接种前进行全面安全检查。
参数说明:
info: 疫苗名称(必填)
示例:
/vaccine check 乙肝疫苗
/vaccine check 流感疫苗
/vaccine check HPV疫苗
执行步骤
添加疫苗接种计划 (add)
1. 解析疫苗信息
从自然语言中提取:
基本信息:
- 疫苗名称:中文或英文名称
- 接种程序:0-1-6、2-6、单次等
- 剂次信息:第几针、已接种剂次、总剂次数
- 接种日期:已接种或计划接种的日期
详细信息(可选):
- 生产厂家:疫苗制造商
- 批号:疫苗批号
- 接种部位:左上臂、右上臂等
- 接种单位:医疗机构名称
- 接种医生:医生姓名
- 不良反应:接种后的反应
2. 查找疫苗数据库
从 data/vaccine-database.json 中匹配疫苗:
匹配规则:
- 完全匹配:疫苗名称完全相同
- 别名匹配:使用 aliases 字段
- 模糊匹配:部分名称匹配
3. 接种前安全检查
重要:在保存疫苗信息之前,必须进行全面安全检查。
3.1 过敏检查
检查流程:
// 伪代码示例
function checkVaccineAllergies(vaccine) {
const allergies = loadAllergies('data/allergies.json');
const warnings = [];
for (const allergy of allergies.allergies) {
if (allergy.current_status.status !== 'active') continue;
// 检查疫苗禁忌症中的过敏原
const isContraindication = vaccine.contraindications.some(c =>
c.type === 'allergy' && c.allergen === allergy.allergen.name
);
if (isContraindication) {
warnings.push({
allergen: allergy.allergen.name,
severity: allergy.severity.level,
reactions: allergy.reactions,
recommendation: getRecommendation(allergy.severity.level)
});
}
}
return warnings;
}
function getRecommendation(severityLevel) {
const recommendations = {
'mild': '可接种,需观察',
'moderate': '谨慎接种,建议咨询医生',
'severe': '不建议接种,或咨询专科医生',
'anaphylaxis': '绝对禁忌,禁止接种'
};
return recommendations[severityLevel];
}
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.
- 12d ago First seen · 1,170 lines · 8 tokens per session scan A f53d8c4fdb68
vaccine is a command published in the GitHub repository huifer/WellAlly-health (948 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 8,336 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.