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/exportgit 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/export)<a href="https://agentmods.dev/commands/bacc-labs/cynthia-generator/export"><img src="https://agentmods.dev/badge/commands/bacc-labs/cynthia-generator/export.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.08152 |
| Opus 5 | $0.00011 | $0.04076 |
| Sonnet 5 | $0.00004 | $0.01630 |
| Haiku 4.5 | $0.00002 | $0.00815 |
Grade A, and why
export scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X GET https://fhir.example.com/fhir/metadata How it starts
The opening of the file, as written. The whole thing — 956 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Synthetic Patient Data
Export generated FHIR-compliant synthetic healthcare data to various destinations including local files, databases, cloud storage, and FHIR servers.
Overview
This command takes generated patient data and exports it to the destination of your choice. Supports multiple formats and destinations to integrate with existing healthcare systems and workflows.
How to Use This Command
Interactive Mode (Recommended)
Simply run:
/export
Claude will ask:
- Export destination (JSON file, CSV, MySQL, S3, FHIR server)
- Format preferences (Bundle, NDJSON, CSV structure)
- Output location or connection details
- Whether to create database tables automatically (MySQL)
Command-Line Arguments Mode
Provide parameters upfront:
/export --destination json --output ./patient-data.json --format bundle
Available Arguments:
--destination json|csv|mysql|s3|fhir|api: Export destination--output PATH: Output file path (for json/csv)--format bundle|ndjson|flat: Format for JSON export--host HOST: Database/FHIR server host (for mysql/fhir)--database NAME: Database name (for mysql)--bucket NAME: S3 bucket name (for s3)
Instructions for Claude
When executing this command:
Step 1: Check for Generated Data
Verify that patient data has been generated:
- Check if data exists in memory from previous
/generatecommand - If no data available, inform user they must run
/generatefirst - Confirm number of patients and resources to be exported
Step 2: Gather Export Parameters
If arguments not provided, use AskUserQuestion to gather:
- Export Destination:
Ask: "Where would you like to export the data?"
Options:
- JSON file: Local file in JSON format
- CSV files: Separate CSV files per resource type
- MySQL database: Direct MySQL database insertion
- S3 bucket: AWS S3 cloud storage
- FHIR server: POST to FHIR R4 server endpoint
- API (bacclabs.io): POST an existing local FHIR JSON file to the Cynthia API
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 · 956 lines · 22 tokens per session scan A 3ec1062a1917
export 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 8,152 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.