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/bacc-labs/cynthia-generator/validategit clone --depth 1 https://github.com/BACC-Labs/cynthia-generatorWrote 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/bacc-labs/cynthia-generator/validate)<a href="https://agentmods.dev/commands/bacc-labs/cynthia-generator/validate"><img src="https://agentmods.dev/badge/commands/bacc-labs/cynthia-generator/validate.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.03190 |
| Opus 5 | $0.00011 | $0.01595 |
| Sonnet 5 | $0.00004 | $0.00638 |
| Haiku 4.5 | $0.00002 | $0.00319 |
Grade A, and why
validate 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 4d 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Synthetic Patient Data
Validate generated FHIR-compliant synthetic healthcare data for clinical accuracy, referential integrity, and structural compliance.
Overview
This command analyzes FHIR Bundles to check:
- Clinical Realism: Lab values, medication dosages, disease progression patterns match medical standards
- Referential Integrity: All resource references (Patient → Condition → Encounter → Observation) are valid
- FHIR Compliance: Resources conform to FHIR R4 specifications (required fields, code systems, dates)
How to Use This Command
Interactive Mode (Recommended)
Simply run:
/validate
Claude will ask:
- Path to FHIR Bundle JSON file to validate
- Severity level to report (all issues, critical only, or critical+warnings)
Command-Line Arguments Mode
Provide parameters upfront:
/validate --file ./synthetic-patient-001.json
/validate --file ./test-data.json --severity critical
Available Arguments:
--file PATH: Path to FHIR Bundle JSON file--severity all|warnings|critical: Which severity levels to report (default: all)
Instructions for Claude
When executing this command:
Step 1: Gather Parameters
If arguments not provided, use AskUserQuestion to gather:
-
File path:
- Ask: "Which FHIR Bundle file should I validate?"
- Default suggestion: Look for recently generated files in current directory
- Check if file exists using Read tool
- If not found: Ask for corrected path or list available .json files
-
Severity level (optional):
- Ask: "Which severity levels should I report?"
- Options: "all" (CRITICAL + WARNING + INFO), "warnings" (CRITICAL + WARNING), "critical" (CRITICAL only)
- Default: "all"
- Explain: "all = comprehensive report, warnings = actionable issues only, critical = must-fix errors only"
Step 2: Verify File Exists
Use Read tool to check if file exists:
Read the first few lines to verify it's valid JSON and a FHIR Bundle
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.
- 4d ago First seen · 490 lines · 22 tokens per session scan A 8dab658c5f9f
validate is a command published in the GitHub repository BACC-Labs/cynthia-generator (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 3,190 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.