Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sigistry/marketplace/plugin install recordsWrote 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/sigistry/marketplace/validate)<a href="https://agentmods.dev/commands/sigistry/marketplace/validate"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/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.1 | $0.00019 | $0.00294 |
| Opus 5 | $0.00010 | $0.00147 |
| Sonnet 5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 2d 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.
What it actually says
Records FHIR Validate
Use /records:fhir-validation behavior for this validation task. Prefer a
configured local Records CLI when available. If no executable local Records
runtime is available, use the local structural fallback and label it as
such.
Target: $ARGUMENTS or the current working directory.
Run the orchestrator, which detects project context, builds a runtime plan, enforces privacy gates, validates each resource, and enriches every issue with fixability guidance and a JSON Pointer:
node "${CLAUDE_PLUGIN_ROOT}/skills/fhir-validation/scripts/validate.mjs" "$ARGUMENTS"
If no argument was provided, use .. Summarize:
- Mode, selected runtime, runtime attempts, and privacy boundary.
- Totals: resources scanned, errors, warnings, information.
- Errors first, grouped by file and path, with the JSON Pointer and whether the fix is mechanical, domain input, or setup/package repair.
- Package doctor findings, detector recommended order, and any missing package dependencies.
Do not edit files unless the user explicitly asks for fixes, and do not claim profile conformance unless the selected runtime actually loaded profile, package, terminology, and invariant context.
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.
- 2d ago First seen · 35 lines · 19 tokens per session scan A 92c967d2938b
validate is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 294 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-09-03.
Other commands, from other repositories
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
review
Pressure-test an important decision, plan, proposal, strategy, architecture, or recommendation with adaptive depth and token-efficient verification.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
compliance-fix
Show Qualimetry review findings for a file and apply the standards-compliant fix.
clean-gone
Clean up local branches that have been deleted from the remote repository.
commit-push-pr
Complete workflow — commit, push, and create a pull request in one step.